▸ THE CHALLENGE
NO-BUY YEAR: HOW TO ACTUALLY GET THROUGH ONE
A no-buy year is a commitment to stop discretionary purchases for a set period; a low-buy year sets a smaller allowance instead of zero. Both fail for the same mechanical reason — the rule lives in your memory, and nothing enforces it at the moment it is broken, which is usually a sale or a bad evening. Enforcing it means blocking the shopping apps during those windows and requiring a delay before any allowed purchase.
Why no-buys break
Nobody abandons a no-buy year deliberately. It ends in one of three ways, and all three are predictable enough to design against:
- A sale. The rule was about not wanting things. The sale is about a price, so it does not feel like the rule applies. See sale events.
- A bad day. The rule was made by someone who felt fine. See retail therapy.
- All-or-nothing collapse. One purchase breaks it, so the year is "ruined", so the rest of the month is spent. The rule had no way to bend, so it snapped.
Low-buy beats no-buy for most people
A rule with no permitted exceptions has to be perfect to survive, and one failure destroys it entirely. A rule with a defined allowance — a number per month, or a category you are still allowed — survives its own failures, which is the only property that matters over twelve months.
Decide the allowance in advance and write it down. An undefined "I'll be sensible" is not an allowance; it is a negotiation you will hold with yourself, later, while shopping.
Make it structural instead of remembered
- Name the windows. Late nights, payday, sale events, bad days. These are where the year will actually be lost.
- Block the apps during them. Not deleted — deleting fails, because reinstalling takes seconds and the moment you want to reinstall is the moment you are least able to talk yourself out of it.
- Route every allowed purchase through a delay. Three days, no exceptions. This is what keeps the allowance from quietly becoming the budget.
- Count what you did not spend. A no-buy year has no visible progress by design — money you kept produces no parcel, no email and nothing to look at. Making that number visible is the only honest scoreboard available.
- Plan the breaks. A birthday, a holiday, a genuine replacement. Scheduled exceptions do not break a rule; unscheduled ones do.
Where Sale Armor fits
Sale Armor is the enforcement layer, not the rule. It blocks the shopping apps you choose during the windows you choose, holds anything you still want for three days, and totals up what you turned down. It has no opinion about your allowance and no streak to break — one broken day cannot make the app disappointed in you, because it does not keep score of you at all.
▸ THE APP
SHUT THE SHOPPING APPS TONIGHT.
Sale Armor blocks the apps you choose during the windows you choose, and holds anything you still want for three days. No account, no bank access, no analytics.
SEE THE PRICEQUESTIONS
A commitment to stop discretionary purchases for a set period, usually with a short list of allowed exceptions such as replacements and essentials. A low-buy year sets a reduced allowance instead of zero.
Because the rule is enforced only by memory, and the moments it breaks — a sale, a bad evening, payday — are exactly the moments memory performs worst. An all-or-nothing rule also collapses completely after a single failure.
Sale Armor works as the enforcement layer: it blocks shopping apps during the windows where no-buys usually break, holds any purchase for three days, and adds up the money you did not spend.