Money tips

Repair or replace? A sunk-cost check with a worked example

Repair or replace your phone? A sunk-cost check with a worked example that compares only future costs and shows why past repair bills should not decide.

Editorial illustration for Repair or replace? A sunk-cost check with a worked example

When deciding whether to repair or replace a phone, ignore what you have already spent on repairs and compare only future costs: the repair bill plus how long it will realistically last, against the price of a replacement over its likely life. Past repairs are sunk cost. They are gone whichever way you decide, so they should not push you to repair again or to give up.

What is the sunk-cost trap with repairs?

It sounds like this: "I have already put ₹5,800 into this phone, so I should keep it going." The money is spent either way. If the phone is likely to fail again, spending more only adds to the loss. The opposite error also exists: "I have wasted so much on repairs, so I should buy a new one right now", even when the current repair is cheap and the phone is otherwise fine. In both cases, the history is steering the decision. Leave it out.

What does a worked example look like?

Say your phone has had a screen repair of ₹4,000 and a battery change of ₹1,800. That is ₹5,800 of past spending. Now the charging port fails and the quote is ₹2,400. A new phone you would be happy with costs ₹15,000. Only the future matters, so list the options.

OptionCost nowExpected extra lifeCost per month
Repair the port₹2,40012 months₹200
Buy new phone₹15,00036 months₹417
Buy new, sell old for ₹2,000₹13,00036 months₹361

Expected life is a guess, so treat it as a range. Divide the cost by the months: 2,400 divided by 12 is ₹200; 15,000 divided by 36 is about ₹417; 13,000 divided by 36 is about ₹361. On these numbers repairing is cheaper per month. If you think the old phone will last only 6 months after this repair, the cost rises to ₹400 a month (2,400 divided by 6), which is close to a new phone. The decision depends on that one honest estimate.

What questions should you ask about the future?

  1. How likely is another failure in the next year? A phone that has had three different repairs in two years is a clue.
  2. Does it still get software and security updates from the maker? Check the maker's support page for your model.
  3. Is it still fast enough for the apps you rely on, such as UPI and banking apps?
  4. Is the battery or storage a daily nuisance, even after the repair?
  5. What is your cost of being without a phone for a few days if it fails again?

How does a repair history help?

It does not tell you what to do, but it gives you data for the estimate. Dates and amounts of earlier repairs show how often things go wrong. If you keep expenses in a tracker such as SpendixAI, you can search the category or merchant for repairs and see the history in one place; you can also keep a receipt alongside the transaction, which helps with warranty questions.

What about the cost of the next phone?

A new phone is also a long-term cost: accessories, insurance if you take it and a data plan. Only count what changes between the two options. If you would pay the same recharge either way, leave it out. Keep the comparison simple enough to do on a sheet of paper.

A short checklist

  • Write the repair quote and the replacement price.
  • Cross out every past repair; do not count them.
  • Estimate months of life for each option.
  • Divide cost by months and compare.
  • Decide, and note the date so you can check your guess later.
SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports