Redesign ROI: How to Prove the Value of Design Changes Before They Are Launched

“We need a redesign,” says the designer. "Why?" says the CEO. “Well, the interface is outdated, users complain, and that’s important,” he says. "No budget," says the CEO.

This conversation happens in every other company. And it's the designer's fault, not because he's wrong about the redesign, but because he speaks the wrong language.

The CEO thinks in terms of money and risk. “The interface is outdated” is not a category of money. “Bad onboarding costs us 200,000 rubles a month of lost retention revenue” is already a conversation.

Redesign ROI is the translation of “need to be redesigned” into business language. Not for politics. For the sake of an honest answer to the question: is it worth it?

## What is ROI in the context of design

ROI (Return on Investment) = (Earnings from Change − Cost of Change) / Cost of Change × 100%

In the context of design:

• ** Profit from the change** - additional revenue or cost savings that the new design will bring
• ** Cost of change** – time and money for design, development, testing, implementation

If the ROI is positive, the redesign is beneficial. If the negative is unprofitable or neutral.

An important nuance: ROI redesign is considered on the time horizon. The redesign is now, paying off gradually. It is necessary to count not only the total amount, but also when it will be reached (payback period).

## Why ROI redesigns are not usually considered

Three honest reasons:

Uncertainty. It is difficult to predict the effect before the changes are implemented. An error of ± 50% is not uncommon.

** Attribution complexity. ** If the redesign has increased retention, is it just a redesign? Or a marketing campaign, and improved support, and a competitor’s exit from the market?

• Really. Calculating ROI requires data, time and the ability to work with numbers.

But uncertainty is no reason not to count. An approximate calculation is better than his absence. Even the order of the number ("this will bring in about X million per year") changes the conversation.

## Three Components of Redesign Income

### Component 1: Conversion growth

The new design converts better. Users are more likely to register, activate, pay.

How do you count

Formula: Additional revenue = Current traffic × (New CR − Old CR) × LTV

** Example:**

• Traffic to the site: 50,000 per month
• Current conversion rate (landing → registration): 3%
• Expected new CR after redesign: 4.5%
• User LTV: 12,000

Additional monthly users: 50,000 × (0.045 − 0.03) = 750 Additional income per month: 750 × 12,000 = 9,000,000 ый (this is a potential future LTV, not immediately)

This is an optimistic calculation – the actual conversion effect should be discounted. But the order of the numbers is clear.

### Component 2: Decrease in churn

Best UX → users stay longer → above LTV → higher total revenue.

How do you count

Formula: Additional revenue = Current user base × (New Retention - Old Retention) × ARPU × Period

** Example:**

• Active subscribers: 5,000
• Current monthly churn: 5%
• Expected churn after redesign: 3.5%
• ARPU: 800 ц/month

Additionally retained users per month: 5,000× (0.05−0.035) = 75 users Additional income per month: 75 x 800 = 60,000 ый

Annually: 720,000 from churn decline alone

### Component 3: Savings on support

Bad UX generates support calls. The good one reduces them. It's real money.

How do you count

We need data: the number of support requests per month, their average processing cost, what percentage is associated with UX problems.

Formula: Savings = Monthly Contacts × Percentage of UX Appeals × Expected Decline × Processing Cost

** Example:**

• Appeals in support: 2,000 per month
• The cost of processing one appeal: 300
• Estimation of the share of UX addresses: 40%
• Expected decline after redesign: 30%

Savings: 2,000 × 0.40 × 0.30 × 300 = 72,000 ия per month = 864,000 ия per year

## How to calculate the cost of a redesign

You have to be honest, otherwise the ROI will be overstated.

Direct costs:

• Design: designer's watch × bet
• Development: Developer's hours x rate
• Testing (QA): clock × bet
• User Research: Recruiting + Conducting

Indirect costs:

• Management and coordination
• Risk of error (sometimes something breaks with a redesign)
• User training when radical changes occur
• Support during the implementation period (more calls during the transition)

Example of onboarding redesign budget:

• Design (80 hours x 3000 ): 240,000
• Development (120 hours x 4,000 ): 480,000
• QA and testing (40 hours x 2,000 ): 80,000
• User research: 60,000
• **Total: 860,000 **

## Calculation of ROI: summary table

Bring it all together:

Cost of redesign: 860,000 а

Payback period: 860,000 / 132,000 ≈ 6.5 months

ROI for the year: (1,584 000 – 860,000) / 860,000 × 100% = **84% **

This means that after investing 860,000 . in the redesign, a year later the business has an additional 724,000 . profit from this investment.

This is not an accurate calculation, this is a reasonable estimate. These are the numbers you need to talk to the CEO.

## How to justify the calculation: working with data

Calculating ROI without data is a fantasy. Data is needed for every assumption.

### Where to get data

Current metrics: Google Analytics, Amplitude, Mixpanel, CRM. Retention, churn, ARPU, conversion rate – all this should be in analytics.

** Support data: * CRM or helpdesk system. Number of applications, their categories, processing time.

**Expected improvements: * This is the hardest part. Several approaches:

• Past A/B test data (if any)
• Industry benchmarks (websites like FirstPageSage, Barilliance publish conversion data)
• Data from usability tests (if you fix specific problems, how many users will stop losing)

**If there is no data, start by collecting it. Ask the analyst to set up a funnel in analytics, conduct a usability test and calculate the error rate. Without a basline, there is no improvement.

## How to give calculation to management

The ROI calculation is not an Excel table that is placed on the table. It's a story with numbers.

** Presentation structure:**

1. The problem is the numbers. Right now we are losing X users in step Y onboarding. This costs us Z roubles a month”.

2. *What do we want to do? We want to redesign the scalp. This is what the new float will look like.”.

3. Why would it help? The problem is that [the specific UX problem]. The usability test data shows that 4 out of 5 users cannot [act specifically]. After correction [specific expected effect].”.

4. **How much does it cost? * Direct and indirect costs.

5. ** What do we get? * Three components of income calculated.

6. When it pays off. Payback period.

7. **Specific metrics before and after.

## Dealing with Uncertainty: Scenario Analysis

The ROI calculation is a prediction. Predictions can be wrong. An honest approach - scenario analysis:

Showing three scenarios, you’re honest with management: “Even in a pessimistic scenario, it’s profitable.”.

The pessimistic scenario must be truly pessimistic. Not “worse than our plan”, but “what if we made a mistake 2 times”.

## The alternative approach: the cost of inaction

Sometimes it is easier not to count the benefits of redesign, but to calculate the cost of inaction – how much we lose if we do not.

Formula: Cost of inaction = Loss per month × 12 months

** Example:** Every month, 35% of users leave onboarding step 3. Of these, 30% would go to payers. With an average LTV of 12,000 ых, this means 100 lost users per month × 0.30 × 12,000 = 360,000 ых per month, or 4,320,000 ых per year of lost revenue.

It's a strong argument: "We need $4.3 million to do nothing.".

## How to calculate if there is no data: a quick approach

Not everyone has mature analytics. Here is the minimum set for calculating ROI:

Step 1. Ask the analyst (or see for yourself in Analytics) the number of users at each key flow step per month.

Step 2. Find the biggest gap is the point of greatest loss.

Step 3. Find the ARPU and the average user lifespan in the CRM or financial data.

** Step 4.** Do 3-5 usability tests specifically at the problem step. Write down how many users failed and what exactly is the problem.

Step 5. Formulate the hypothesis: “If you fix this problem, X% more users will move to the next step.”.

That's enough for a rough ROI calculation.

## After the redesign: how to prove that everything worked

Rationale ROI prior to redesign is a hypothesis. Confirmation after is a fact.

What to measure:

• The same metrics used in the ROI calculation (CR, churn, number of support calls)
• With the same comparison period (preferably the A/B test, if not - "before / after" with a control period)

What to fix:

• Distribution of “was/became” by each metric
• Actual financial effect in rubles
• Deviating from the forecast and explaining why

Why would you do that

1. Learning to make better predictions for the future
2. Create trust in the team ("designers say something and it comes true")
3. Build the basis for the following budget rationale

## Template to justify redesign

Problem
[Specific flow/screen] shows [metric] = [value].
That means we lose [X users] in [period].
Cost of losses: [Y rubles/month].

SOURCE OF THE PROBLEM
The usability test (N = [quantity]) showed:
[X of N] users have encountered [a specific problem].
Main reason: [Description].

Proposed decision
[Short description of the redesign].
Key changes: [List].

The expected effect
[Metrica] will improve from [X%] to [Y%] in the baseline scenario.
Financial effect: + [Z rubles/month].

Cost
Design: [N hours x bet]
Development: [N hours x bet]
Total: [Amount]

ROI AND PAYBACK
Payback period: [N months]
ROI for the year (baseline scenario): [X%]
ROI for the year (pessimistic): [Y%]

How to measure success
Metric 1: [Name] - the goal [value] through [period]
Metric 2: [Name] - the goal [value] through [period]

## Outcome

ROI redesign is not the magic of finance. It is a discipline to collect data about a problem, formulate an improvement hypothesis, calculate cost and expected benefit.

A designer who can do this is not just a designer. This is a person who speaks the language of business and takes part in strategic decisions.

This is the kind of designer who gets the redesign budget.

## Soft justification: when numbers are lacking

Sometimes the data is not enough for a rigorous ROI calculation. This is not to say that the redesign cannot be justified – you need to use other arguments.

### Competitive analysis

Our main competitor X redesigned the onboarding three months ago. According to open data, their retention increased by [N]%. Our onboarding has similar problems.”.

This is not a direct financial calculation, but it is an argument that businesses understand: lagging behind a competitor has a real cost.

### NPS and Quality Feedback

“In the last three months, we have received 47 complaints about [specific flow]. Of these, 12 came from paying users. Here is a typical quote: [...]”.

Qualitative data translates the abstract “users are uncomfortable” into concrete, live voices. This works especially for empathic leaders.

### Benchmarking with the industry

The average conversion rate for SaaS onboarding is 55-65%. Ours is 38 percent. The gap of 17-27 percentage points is directly translated into lost users.”.

Public benchmarks are a valuable argument. Sources: Barilliance, Baymard Institute, FirstPageSage, Mixpanel and Amplitude industry reports.

## How to convince the development team: a separate task

A redesign ROI needs to be sold not only to the CEO, but also to the development team. Developers have other concerns and a different language.

What worries developers:

• Technical Debt from Bad Design
• Constant changes (made, then remade)
• Fuzzy requirements

How to talk to developers:

• Show the data: " Support is now getting 200 calls a month about [issue X]. That means X hours of team time. After the redesign, it will go.”.
• Explain the technical debt of the redesign: Current flow requires the support of 3 different UI patterns for a single action. After the redesign, one. This will simplify the code.”.
• Give clear specifications before the developer starts, not at the time.

## What to do if the ROI is negative

Honest calculation sometimes shows that redesign does not pay off in a year. What then?

Option 1: Limit Scope. Instead of a complete redesign, a spot improvement on a specific problem. Cost lower, ROI higher.

Option 2: Find other components of income. Maybe the ROI is negative because it doesn't account for all the effects. The impact on NPS, on lower support costs, on App Store rankings — all of this is real money that’s easy to miss.

** Option 3: Modify the time horizon.** ROI negative for a year but positive for 2 years? That's another conversation. Not all investments pay off quickly.

** Option 4: Honestly refuse. ** Sometimes a redesign is really not a priority right now. Honesty in ROI sometimes means saying, “Right now, other things are more important, let’s get back to that next quarter.”.

A designer who knows how to honestly count ROI—including when the result is not in his favor—is far more trustworthy than someone who sells any solution as the obvious winner.

## The role of design in business strategy: a long-term perspective

The ROI of a particular redesign is a tactic. But the bigger question is, how does design create a competitive advantage in the long run?

Apple has used design as a strategic asset — a differentiator that allows products to sell more than competitors. Premium UX = premium price.

*Airbnb invested in professional housing photography during the crisis. The conversion has grown so much that it has paid off many times over. The design solution saved the company.

**Booking.com owes a significant share of its success to the thousands of A/B tests that optimized each step of the funnel. The culture of experimentation is a competitive advantage.

In each of these cases, design is not “decoration,” but a strategic decision with measurable business results. The ROI of a particular redesign is one step in that direction. But more importantly, we need to understand that design is an investment, not an expense.

## Template: Redesign roadmap for internal presentation

When ROI alone is not enough, a structured roadmap is needed to show the business exactly what will happen and when.

REDISAIN ROAD MARK [NAME FLOW/PRODUCT]

Current state
Metric 1: [value] (benchmark: [norm])
Metric 2: [meaning]
Value of current state: [X] /month

Issues (prioritized)
1. Influence: [Y] ма/month
2. Influence: [Z] ма/month

PLAN OF WORK
Phase 1 (2 weeks): [what we do] → Expect [metric]
Phase 2 (3 weeks): [what we do] → Expect [metric]
Phase 3 (1 week): Test and iteration

Resources
Design: [N] hours
Development: [N] hours
Total cost: [Amount]  

Expected outcomes
After 1 month: [metric] improves to [value]
After 3 months: ROI [X]%
After 12 months: ROI [Y]%

Risks and Mitigation
Risk 1: [Description] → Mitigation: [How to reduce]
Risk 2: [Description] → Mitigation: [How to reduce]

How successful we are
[Metrica] reached [meaning] through [term]
● The cost of support decreased by [N]%
NPS improved by [N] points

## AI and ROI Redesign: How to Calculate Value and Convince a Business

AI doesn’t replace real-world data, but it helps to structure argumentation, model scenarios, and frame the calculation so that the CEO understands.

### Prompt: calculate the ROI redesign

Help me calculate the redesign ROI.

Current data:
- [The metric we want to improve]: [current meaning]
- Expected improvement after redesign: [% hypothesis]
Traffic/active users: [number]
- ARPU: [sum]  
LTV: [sum] ) (or churn rate: [%])
- Number of support requests for this issue: [number/month] (if any)
- Cost of processing: [Amount] ) (if any)

Cost of redesign:
- Design: [clock × bet]
- Development: [clock × bet]
- Research: [sum]

Calculate:
1. Additional revenue from improving metrics
2. Savings on support (if applicable)
3. Total annual effect
4. Payback period
5. ROI in 12 months

Also do script analysis (pessimistic/basic/optimistic).

### Prompt: Finding the "cost of inaction"

Sometimes it is easier to justify how much it costs not to redesign:

Help calculate the cost of inaction for [a problem in the product].

Data:
- Problem step: [Description]
Drop-off on this step: [%]
Users who reach this step per month: [number]
- User LTV: [Amount]  
- Conversion further down the funnel to the payer: [%]

Calculate:
1. How many potential payers do we lose each month?
2. LTV of these lost users
3. The cost of inaction in a year

Make 2–3 sentences for the slide “Why You Should Do It Now.”.

### Prompt: Prepare to talk to CEO

I have to defend the redesign budget to the CEO.

Here's my data and my calculations:
[Put the numbers in]

Help me prepare:
1. What questions will the CEO ask? Prepare answers for each
2. What objections to expect and how to respond to them?
3. Translate my data into business language (money, risks, deadlines)
4. What is the weakest point in my argument and how can I strengthen it?

### Prompt: make an executive summary of the redesign

After protection, you need a document on 1 page:

Here are all the details of our redesign project:
[Insert data: problem, solution, calculations, plan]

Write an executive summary on page 1 for guidance.

Structure:
Problem (2-3 sentences with numbers)
Decision (2-3 proposals)
- Expected result (1-2 sentences with main figures)
- What you need (resources, deadlines)
- Next step (specific, one)

Tone: Direct, without UX jargon, focused on business results.

### Prompt: Measure the result after the redesign

After launch, you need to confirm that the calculation was correct:

So we started redesigning [that] [date].

Data before redesign:
[metrics]

Data after (period [X weeks]):
[metrics]

Analyze:
1. What metrics have changed and by how much?
2. Is the result consistent with the forecast (was: [the forecast])?
3. If there are deviations, what are the possible explanations?
4. What is the actual ROI over the past period?
5. What does this say about the quality of our forecasting methods?

Help me write an internal report for the team.