You spent $250 on a pair of boots last spring. You wore them maybe twelve times. That's $20 a wear, and the math is going to get worse before it gets better — those boots are still in the closet and you've already moved on to the next thing.

You spent $14 on a pack of three white tees. You wear them six days a week. Eight months in, one is yellow at the collar, one stretched at the neck, the third still hanging on. Call it 144 wears across three shirts. Forty-six cents a wear. That's the math.

Cost per wear is the cheapest piece of clothing math there is. It is also the only one that tells the truth.

Cost per wear catches what every other metric misses

The retail industry has trained men to evaluate clothing by sticker price. Is $80 too much for a tee? Is $400 reasonable for a jacket? These are the wrong questions. The right question is what each item will cost you across its actual life.

The formula is one line: dollars in, divided by times worn. A $200 shirt worn 200 times costs a dollar a wear. A $40 shirt worn twice costs $20 a wear. The cheap shirt was five times more expensive.

Cost per wear catches the regret hiding inside a sale price. It catches the value hiding inside a "splurge." It exposes the items that looked great in the photo and never left the drawer. Most men have a closet full of cheap mistakes and a small drawer of expensive workhorses — and the math, finally, names both.

Quality has a breakeven. Cheap doesn't

There is a number inside cost per wear that most retail copy hides: the breakeven point. The wear count at which a more expensive item becomes cheaper per wear than a cheaper one.

A $30 t-shirt that lasts 50 wears costs sixty cents a wear. A $14 t-shirt that lasts 12 wears costs $1.17. The $30 shirt was cheaper before you finished its second month.

This is the math that ends the "I can't afford the nice one" objection. The nice one is the affordable one — usually inside six months. The cheap one is the expensive one that nobody admits is expensive because the receipt is small.

The catch: it only works if you actually wear them. A $400 jacket that lives in your closet because you "save it for nice occasions" has a CPW of $400. The cheap one beats it by a wide margin.

The variable that matters is the wear count, and nobody tracks it

Here is where cost per wear stops being useful for most people: nobody actually knows how many times they wore anything.

You can guess. Most men guess high. You will swear you wore the navy crewneck "all the time last winter" and then realize you wore it eleven times before the elbow pilled and you stopped reaching for it. The brain compresses memory toward the items it likes; the closet does not.

Put more simply: the formula is easy. The data is the hard part. And men have built their entire wardrobe behavior around not collecting that data.

Without a wear count you trust, cost per wear is a vibe. It is the dieting equivalent of "I'm pretty sure I'm eating clean" — the framework is right, the inputs are made up, and the conclusions are flattering by design.

What the math actually reveals

Run the numbers across a real closet and three patterns surface every time.

First, the items you actually rotate are an order of magnitude cheaper per wear than you would expect. Your daily socks, your default crewneck, your one pair of jeans — these are workhorses, and the math rewards workhorses brutally. The cost per wear on your most-used item is almost certainly under a dollar.

Second, the "investment pieces" are the worst offenders. The expensive jacket worn six times. The dress shirt bought for a wedding three years ago. The chinos that fit weird that you keep meaning to tailor. Cost per wear flags these mercilessly. They sit at the top of the worst-value list every time.

Third, the saved multiples are dead money. The three identical navy tees in the drawer — one in rotation, two in storage — divide your wear count across three items but your purchase cost is full triple. The math punishes the stockpile.

These patterns are the real indictment of how men shop. Not "you bought too much." Not "you bought the wrong things." The pattern is: you did not buy enough of what you actually wear, and you bought too much of what you do not.

Tracking is the work. The math is the easy part

Once you accept that wear count is the variable that matters, the implementation problem stares back at you. How do you count?

The honest answer is you do not, by hand. Nobody is going to tick a chart every morning. The men who try last two weeks and quit. The math has been right for decades; the practice has been absent because the data collection is annoying.

The fix is to put the counting somewhere it can run on its own. Tag the daily rotation. Log the defaults. Anchor each item to the exact product so the system knows what it is tracking and when to flag the rotation cycle. That is the infrastructure cost per wear has been missing. The formula was always right. The system layer is what closes the loop.

The verdict

Cost per wear is the only piece of clothing math that does real work. It will tell you which $200 jacket was a steal and which $20 sale-rack tee was an expensive mistake. It punishes hoarding, exposes regret, and rewards the items you reach for without thinking.

But the formula is only as good as your wear count. And your wear count is only as good as the system tracking it. Either you build that system or you do not, and the wardrobe you end up with reflects that choice.

If you have ever wondered which of your clothes are actually paying you back, Rotation answers that question. It anchors your go-to products, tracks what you wear, and reorders the workhorses before they fail. The math runs itself.

Cost Per Wear: The Only Wardrobe Math Worth Doing