RMOIRE/JOURNAL/COST-PER-WEAR

Cost-per-wear: the only math that matters when you shop.

No. 02·April 22, 2026·5 min read·METHOD

A two-hundred dollar jacket worn one hundred times costs two dollars per wearing. A thirty-dollar top worn twice costs fifteen. Stated like that, the math is so obvious it feels insulting to point out. It's also the single number that most people never run before buying something, which is the entire reason their closets look the way they do.

Cost-per-wear is exactly what it sounds like: take what you paid, divide by how many times you've worn it. The formula is so simple it would be pointless to write about if not for the fact that nearly every framework that competes with it — "is it on sale?", "do I love it right now?", "is it a wardrobe staple?" — is worse at predicting whether you'll regret the purchase.

The math that beats sticker price.

Here are three small case studies you've probably lived through some version of:

You buy a $480 wool overcoat in October. You wear it nearly every day from November through March for three winters running. Call it 250 wearings. The coat cost you about $1.92 per outing. By the third winter people start to ask where you got it.

You buy a $40 graphic tee because it's on a 30%-off rack and the color is good. You wear it once, decide the cut is wrong, and it lives in a drawer for two years before donation. $40 per wearing.

You buy a $180 pair of leather sneakers that look right with both jeans and trousers. You wear them about twice a week for two years. Roughly 200 wears. 90 cents per wearing.

None of this is news. What's interesting is that all three purchases would have passed the "is this a good deal?" test at the moment of swiping the card. The $40 tee was on sale. The $480 coat was the most expensive thing in the basket. Sticker price doesn't tell you anything useful about what something will actually cost you to own.

What cost-per-wear is really measuring.

It's tempting to read cost-per-wear as a frugality framework — buy less, buy cheaper, save money. That's not quite it. The number is doing something more interesting: it's converting a one-time purchase decision into a use prediction. When you ask "how often will I actually wear this?", you're forced to think about the rest of your wardrobe, your weekly schedule, your climate, and the occasion frequency for this category. That's a very different question from "do I want this right now?"

The honest answer is usually sobering. A piece you'll only wear to weddings will get worn maybe three times a year. A piece that works for office and weekends will get worn fifty. Versatility is just cost-per-wear in disguise.

Versatility is just cost-per-wear in disguise. The pieces that work everywhere are the ones whose effective cost falls fastest.

Three rules of thumb that make this practical.

Set a target before you buy. Pick a per-wear number that feels fair to you — most people land somewhere between $1 and $5. Now ask: at this price, how many wearings would I need to hit my target? If the answer is "more than I plausibly will," don't buy it. A $200 wedding-guest dress at a $5-per-wear target needs 40 wearings. Are you going to 40 weddings in this dress?

Discount the future. "I'll wear it all the time" is a forecast made by your most optimistic self at the most flattering moment of the shopping experience. Cut your prediction by at least 30 percent before you do the math. If it still pencils out, fine.

Reject the absolute floor. Counterintuitively, very cheap clothing often has the worst cost-per-wear, because it falls apart, fits poorly, or styles in only one way. A $15 top that lasts three wears is more expensive than a $90 top that lasts a hundred. "Cheap" is a number; "inexpensive to own" is a different number.

The wardrobe-gap version of the question.

Cost-per-wear sharpens into something almost surgical when you pair it with a digital wardrobe. Once you can see what you own, you can also see what you reach for — which items are doing all the work, and which are taking up shelf space and bringing in nothing. Items with high effective cost-per-wear are dead inventory. Items with low cost-per-wear are infrastructure.

This is where the shopping question flips. Instead of "what do I want?", you start asking "what would unlock 10 new outfits from what I already own?" — and that piece, the one that turns 3 dormant items into rotation again, has an absurdly good cost-per-wear from day one. It's the highest-leverage purchase you can make.

This is also the most common case for a recommendation engine. Tools like RMOIRE track what you wear and help you identify which items earn their keep, and — more usefully — which one missing piece would put the most of your existing wardrobe back into play. The math doesn't change; the visibility does.

One closing reframe.

The mistake almost everyone makes is treating clothes as a stream of independent purchases. Each item is decided on its own merits, in isolation, at the moment of buying. The closet at the end of this process is the union of fifty unrelated decisions, which is exactly why it's so easy to own a hundred and forty items and still feel like you have nothing to wear.

Cost-per-wear quietly forces the opposite. It anchors each purchase to actual life: your week, your weather, your other clothes. Run the math. Most of the time it makes the decision for you.