Tithi Mondal

Article6 min readUpdated

Cost of Bad Design: Rework, Support Calls, Lost Enquiries

See the real cost of bad design: rework in development, support calls from confusing screens and lost enquiries, with a worked rupee example.

By Tithi Mondal, UI/UX Designer

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

Cost of Bad Design: Rework, Support Calls, Lost Enquiries: cover illustration

What is the cost of bad design?

The cost of bad design is the money and time you lose because a screen, form or page is hard to use. It rarely appears as one bill. It shows up as developer hours spent redoing work, staff hours spent answering the same question, and customers who leave without telling you why.

Imagine a pharmacy owner in a small town. Every day she receives 40 WhatsApp messages asking "Where is my order?" Her app has an order screen. It just does not say where the order is. That is bad design, and she pays for it every day.

This article shows where the cost hides and how to count it. For the price of good design, see UI/UX design cost in India. Here we look only at the other side of the ledger.

Where does rework cost in development come from?

Rework cost comes from changing something after it is built. Building a screen, testing it and fixing its errors takes developer days. Changing it later repeats all three steps.

Rework usually has four causes:

  • The flow was never drawn, so the developer guessed the order of steps.
  • The owner saw the screens only after they were built, and then asked for changes.
  • Two screens were built in different styles, so one must be redone to match.
  • A missing case was found late, such as what happens when payment fails or the network drops.

Take a hypothetical example. Suppose a booking app has a checkout of 5 screens. Suppose each screen costs 1.5 developer days to build and test, and a developer day costs ₹2,000.

  • Building the 5 screens: 5 × 1.5 × ₹2,000 = ₹15,000.
  • The owner then decides that login should come after browsing, not before. All 5 screens change.
  • Rebuilding: another ₹15,000.

The same decision, made in a design file before building, costs a few hours of a designer's time. The numbers are invented, but the pattern is real. Late decisions multiply. For more on this, read design before development: why order matters for cost.

How do confusing screens create support calls?

A confusing screen creates a support call every time a customer cannot finish a task alone. Each call costs staff time, and it costs the customer patience.

Common examples of bad UX that cause calls:

  • An order screen with no status, so customers ask where the order is.
  • An error message that says "Something went wrong" and nothing else.
  • A payment screen where the customer cannot tell if the money was taken.
  • An icon with no label, so the customer does not know what it does.
  • A form that clears everything when one field is wrong.

Suppose a small business gets 60 such questions a day. Suppose each takes 4 minutes.

  • Time per day: 60 × 4 = 240 minutes, which is 4 hours.
  • Over 26 working days: 4 × 26 = 104 hours a month.

If a clearer screen removes half of those questions, that is 52 hours a month back. Read how good design reduces support calls for the specific fixes.

How do you count lost enquiries?

You count lost enquiries by comparing how many people start something with how many finish it. The people who start but do not finish are the lost enquiries. They wanted to reach you. Your page stopped them.

Here is a hypothetical worked example. The numbers are invented to show the method.

Suppose a coaching centre website has an enquiry form. Each month, 600 visitors open the form and 30 send it.

The form has 11 fields and asks for an OTP (one-time password) before sending. Many parents give up. Suppose a simpler form with name, phone number and class asks only 3 fields and gets 45 submissions from the same 600 visitors.

  • Extra enquiries: 45 − 30 = 15 a month.
  • Suppose 1 in 3 enquiries becomes a student: 15 ÷ 3 = 5 students.
  • Suppose a student pays ₹12,000: 5 × ₹12,000 = ₹60,000.

In this example, one form costs ₹60,000 a month in missed fees. The arithmetic is simple. The inputs are guesses, so use your own. To find your real numbers, count form starts and form sends for one month. Read form design best practices.

Why do owners miss the cost of bad design?

Owners miss it because nothing sends a bill. A developer invoice is a clear number. An hour lost to a repeated question is not. A customer who leaves a form half filled sends no message at all.

The cost is also spread thin. One confusing screen costs a few minutes on each of many days. No single day feels expensive. Added over a year, it is large. This is why a simple count, even a rough one, is more useful than a feeling.

Write down three numbers this week: how many support questions you get a day, how many people start your main form, and how many finish it. These three numbers turn a vague worry into something you can compare with a design fee.

What other costs does bad design carry?

Some costs are harder to count but still real.

  • Trust. A page that looks careless makes a first-time customer doubt the business. In India, people often pay by UPI to a stranger's account, so doubt matters.
  • Reviews. A customer who got stuck may leave a low rating, and a rating stays public.
  • Team morale. Staff who answer the same question 60 times a day get tired.
  • Slow growth. Every fix you make later takes time that could go into new features.

You cannot put a rupee value on each of these. You can still notice them.

When is bad design a cost you can accept?

Sometimes living with rough design is the right choice. A fair article should say so.

  • A very early test. If you are showing a rough product to ten people, polish is a waste. Accept the rough screens and learn quickly.
  • An internal tool for two staff. If two people use a tool daily and can ask each other, small confusions cost little.
  • A page few people see. An old page with almost no visitors is not worth a redesign.
  • When the fix costs more than the loss. If a problem costs you ₹500 a month and the fix costs ₹30,000, wait.

The test is arithmetic. Estimate the monthly loss, estimate the fix, and divide. If the fix pays back within a few months, do it. If it takes years, leave it.

How do you find the costly problems first?

Start with the screens where money or trust changes hands: the enquiry form, the checkout, the order status. Fix those before the rest.

A short audit can find them. Use the UX audit checklist to walk through your own product, and signs your website needs a redesign to judge whether a fix or a full redo is needed.

Then watch five real people try one task. You will see the problem within minutes.

If you want a second pair of eyes on one flow, you can describe it on my UI/UX design page and I will tell you plainly where I think the cost is hiding.

Frequently asked questions

How can I measure the cost of a bad form or page?

Count how many people start and how many finish for one month. Multiply the missing finishers by the value of one customer. This gives a rough monthly loss.

What are common bad UX examples in Indian apps?

Missing order status, unclear payment results, OTP that does not fill automatically, and forms that clear after one error. Each one causes support calls or drop-offs.

Is fixing bad design always worth it?

No. If the monthly loss is small and the fix is large, wait. Fix the screens that touch money or trust first.

Working on something like this?

Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.

Have a product in mind? Let us design it properly.

Tell me what you are building. I will reply with questions, a rough timeline and a quote.