A dollar is fungible. One dollar spends identically to another. You don't mourn any specific bill. This is the whole point of currency — it is a unit of exchange precisely because it is interchangeable.

An hour is not fungible. The hour between 2 and 3 PM on Tuesday is not the same hour as 2 to 3 PM on Saturday. And neither is the same as the hour between 2 and 3 PM on the last Saturday of your life, which exists and will arrive.

This asymmetry is the whole reason HourSpend exists. Loss aversion, the cognitive bias that Kahneman and Tversky showed in 1979 where losing $100 feels about 2.5× as bad as gaining $100, turns out to be weirdly dormant when the $100 is abstract money. A phone upgrade feels like "a purchase." A phone upgrade relabeled as "4.5 hours of the life you have left" feels like giving something specific up. That's when the aversion wakes up, and decisions get better without anyone getting nagged.

Three tricks to make the relabel stick

1. Never look at a price in isolation

Any time you see a price online and you're even slightly torn about the purchase, do the conversion before you tap Buy. The math:

hours = price ÷ your real hourly wage

If you earn $18 an hour real (see this post on calculating it), a $72 purchase is 4 hours. The hours number and the decision number get bound together in memory. A week later you don't remember "oh yeah I spent $72"; you remember "oh yeah that cost me half a Saturday." The second memory is actionable.

2. Keep the tradeoff concrete

Hours are still abstract until you pin them to something. The trick is asking the second question: what would I actually trade those 4 hours for, if I had them instead?

For most people, 4 hours is a long walk with a friend, or a morning of the hobby they keep saying they miss, or a slow breakfast with their kid. Make the comparison real. The purchase either wins against the specific alternative, or it doesn't. "I want the phone more than a morning with my dad" is a fine answer; it's just no longer automatic.

3. Watch for the frame flip

The same purchase can be bought impulsively ("I deserved it") or reflectively ("I weighed this against the life-hours it cost"). The difference is not usually the purchase. It's the frame the buyer was in when they decided. One rule: if you can't name the hours, you're in the wrong frame. Wait until you can. If it turns out the number embarrasses you, that's useful information. If the number feels right for what you got, buy without guilt — you did the work.

The counter-argument

There's a real objection to all of this: isn't this a recipe for scarcity-thinking? Won't I stop enjoying anything if every latte is a 20-minute calculation?

No, and this is important. The goal of hours-framing is not to push every spending decision toward No. It is to make every spending decision visible, so the Yeses you give are real Yeses. A life where you bought the expensive coffee because you thought about it and decided it was worth 20 minutes is a better life than one where you bought the expensive coffee on autopilot because a latte was "only five bucks." The second version is cheaper per day but more expensive per year, because the cumulative unreflective spends drain hours you didn't know you were giving away.

Practical workflow

HourSpend codifies this into a three-state decision on every expense — bought, thinking, passed. You can log an expense before you commit, sit with the hours number, and decide. If you pass, the amount goes into a Saved Pool you can later allocate to a goal or investment. If you buy, at least the decision was reflective.

That's it. The whole thesis is one observation: dollars feel different than hours, so show the hours. Everything else is scaffolding.

If you want to try it: the free calculator handles any price you type in. The iOS app does it automatically for every expense you log.