Introduction
In our last lesson, you learned how to calculate the monthly revenue being lost due to a specific leak in a SaaS funnel. This is a powerful way to frame your value, but it's only half of the story. Many critical usability issues don't stop a sale—they just make the user's life difficult, leading them to contact customer support. This drains company resources every single day.
Today, we complete the ROI picture. This lesson focuses on another critical, high-leverage skill: estimating the potential support cost savings from fixing a single usability issue. By combining revenue gain (what they get) with cost savings (what they stop losing), you build an unassailable business case for your audit and the follow-on redesign project.
By the end of this 60-minute lesson, you will be able to calculate the direct financial savings from reducing support tickets and build a reusable calculator in Figma to present this to clients.
1. The Hidden Cost of Inefficiency
When we talk about bad UX, we often think of lost sales. But for many companies, especially those with complex products, the more significant drain is internal inefficiency and the direct cost of support. A confusing interface doesn't just frustrate users; it creates a direct operational cost. Sometimes, the consequences can be catastrophic.
To understand the real-world stakes, let's look at an infamous case where a poorly designed internal tool led to a staggering financial loss.
The Real Business Value of UX: How Bad UX Cost Citi $900 Million
This video, 'The Real Business Value of UX', from the vaexperience channel, analyzes how Citibank accidentally wired $900 million due to a confusing internal tool UI. It's a dramatic example of how 'minor' UX issues in non-customer-facing software can have massive financial consequences.
Watch the segment from 00:35 to 05:40. Pay close attention to how the presenter breaks down the flawed UI and the failed 'six-eyes' process. This isn't just about the money; it's about how poor design makes human error almost inevitable. This is a case study you can verbally reference in client calls to illustrate the risk of neglecting internal tool UX.
While the Citibank example is extreme, the principle applies to every company. Every support ticket generated by a confusing feature is a small, recurring cost that adds up. Your job is to find those issues and quantify the cost.
2. The ROI Calculation for Cost Savings
The method for calculating cost savings is straightforward and very defensible. Nielsen Norman Group, a leader in UX research, provides a simple four-step framework.
Calculating ROI for Design Projects
This short video, 'Calculating ROI for Design Projects' by NNgroup, provides a clear, high-level overview of the exact process we're going to follow. It introduces the core concept of converting a UX metric (like support tickets) into a KPI (like cost savings).
Watch from the beginning to 02:55. This will give you the complete mental model. Focus on the example where they connect a reduction in support tickets directly to a monthly dollar saving. This is the exact calculation we will be doing.
The core formula is simple:
The challenge isn't the math; it's finding the right numbers, especially the "Cost Per Ticket."
3. Finding the "True" Cost Per Ticket
Most clients, especially at startups, won't know their "fully loaded" cost per support ticket. They might think of an agent's hourly wage, but that's just the tip of the iceberg. This is an opportunity for you to demonstrate expertise.
Instead of asking "What's your cost per ticket?", you can guide them to estimate it by asking about its components.
The True Cost of Customer Support: 2025 Analysis
This article, 'The True Cost of Customer Support', provides a detailed breakdown of what goes into the total cost per ticket. This is your cheat sheet for having an intelligent conversation with a client about their support costs.
Read the sections 'Defining the True Cost Structure of Customer Support' and 'How to Calculate Your Own Cost Per Ticket'. Pay special attention to the cost components: agent salaries (fully loaded), software/tools, and overhead. The example table breaking down a $950,000 annual budget is the key takeaway. You don't need to memorize the percentages, just understand the categories so you can help a client build a realistic estimate.
When a client says they don't know their cost per ticket, you can now respond with:
"That's common. We can get a quick, conservative estimate. What's the approximate fully-loaded annual salary for a support agent? And roughly how much does the team spend on software like Zendesk or Intercom? What about total tickets per year?"
This changes the dynamic and positions you as a business-savvy consultant.
4. Action: Build Your Support Cost Savings Calculator
Now, let's turn this methodology into another reusable asset in your Figma project. You will create a component that calculates and presents the potential savings from fixing a specific usability flaw.
We will use a concrete scenario.
Scenario: A SaaS product has a confusing process for adding a new user to a team account. Analytics show it's a major source of support tickets.
- Navigate to your Figma project file. Create a new frame next to your "Revenue Leak Analysis" component. Title it "Support Cost Savings Analysis."
- Use the following structure and data to build your calculator. The goal is a well-designed, client-ready asset.
1. Usability Issue Analysis
- Identified Issue: Confusing 'Invite Team Member' flow. Users are unable to find the invitation settings, leading them to contact support.
2. Key Metrics (From Support System & Client)
- Total Monthly Tickets for This Issue: 180 tickets
- Estimated Ticket Reduction Post-Redesign: 75%
- Projected Monthly Tickets Reduced:
180 × 75% = 135
3. Cost Per Ticket Calculation
- Annual Support Agent Salary (Fully Loaded): $65,000
- Number of Agents: 4
- Total Annual Labor Cost:
$65,000 × 4 = $260,000 - Annual Software/Overhead Cost: $40,000
- Total Annual Support Cost:
$260,000 + $40,000 = $300,000 - Total Annual Tickets: 30,000
- Estimated Cost Per Ticket (CPT):
$300,000 / 30,000 = $10.00
4. Monthly Cost Savings Calculation
- Formula:
Monthly Tickets Reduced × Cost Per Ticket - Calculation:
135 × $10.00 = $1,350
5. Business Impact Summary
- Conclusion: The confusing 'Invite Team Member' flow is costing the company an estimated $1,350 per month in avoidable support interactions.
- Annualized Impact: This represents an unnecessary operational cost of $16,200 per year.
For a more detailed, step-by-step walkthrough of this calculation, refer to the example in the NNgroup article you read earlier.
Calculating ROI for Design Projects in 4 Steps
The article 'Calculating ROI for Design Projects in 4 Steps' provides the clearest written example of this calculation. Use it as a reference to double-check your logic as you build the Figma component.
Review the section 'Step 3: Convert the UX Metric into the KPI' and its health-insurance example. This will reinforce the calculation you are performing in your deliverable.
Your final Figma component should look clean, professional, and easy for a non-designer (like a founder) to understand immediately.
Conclusion
You now have the second pillar of your financial argument. You can not only project how much revenue your UX improvements will generate, but also how much they will save. This dual approach is incredibly compelling for business leaders.
Key Takeaways:
- Bad UX doesn't just lose sales; it creates significant operational costs through support tickets.
- The formula for savings is
Tickets Reduced × Cost Per Ticket. - Demonstrate your expertise by helping clients calculate their "fully loaded" cost per ticket, including salaries, software, and overhead.
- Frame the final number as a monthly and annual cost to create urgency and demonstrate the long-term value of fixing the issue.
Preview of the Next Lesson:
We've established how to calculate the financial impact of UX issues. But how do you find the most costly problems in the first place? In the next lesson, we move from quantitative analysis to qualitative investigation. You will learn to interpret click heatmaps to identify rage clicks, dead clicks, and ignored CTAs, giving you visceral, visual evidence of user frustration to pair with your financial calculations.