Graceful Tier Decay: Membership That Fades Instead of Breaking

August 25, 2026

Overview

Paid membership almost always works as a switch. You pay, and you are in. The period ends without a renewal, and you are instantly out. Every tier system built this way has the same shape: a level that is stored somewhere, and an expiry date that flips it off.

That cliff is a poor fit for how people actually pay. People are in a paying mood sometimes and not others. Someone who gave generously for six months and then paused is treated exactly like someone who never paid at all, the moment the clock runs out. And someone who pays far more than a tier costs gets nothing extra for it beyond that same fixed expiry date. The switch flattens generosity and punishes a pause.

Graceful Tier Decay replaces the on/off switch with a value that fades. Each payment holds its full value for an active window. Then, instead of expiring, it ramps down continuously toward zero over a defined decay period. The member’s tier is derived at read time from the summed remaining value of all their payments. Nothing is stored as a level, so nothing goes stale.

That is the entire change: one boolean becomes one number that decreases with time. Everything else in this post follows from it.

The mechanism was devised by Parham Paziraie. It was first worked out and first put into practice in ComeFront, where the summed decaying value drives the Backer Badge.

Key Features

A payment has two phases, not an expiry

Every payment carries its own time anchor and moves through the same two phases, independently of every other payment:

Active: for a fixed window after the payment, it counts in full.
Decaying: when the window ends, the payment does not vanish. Its value ramps down continuously toward zero at a defined rate, and contributes whatever is left of it at the moment the tier is read.

The ramp is a smooth slope, not a staircase. A payment can sit partway between two tiers on any given day, and it crosses a tier boundary the moment its remaining value crosses the threshold.

What follows from a fading value

Four behaviors that membership systems normally have to build as separate features come out of the decay curve for free:

Paying more buys a longer tail, not just a bigger badge. A payment well above a tier’s price keeps its holder at that tier past the active window, then walks them down through the lower tiers over a long remembrance period. Generosity becomes durable instead of being flattened to the same expiry date as the minimum payment.
Stopping steps down instead of switching off. Someone who paid exactly one tier’s price and then stopped does not lose everything at once. They pass through the lower tiers in turn as the value decays, and reach zero only at the end of the slope.
Returning is a top-up, not a restart. The previous payment’s remainder is still counted, so a lapsed member who comes back adds to what is left rather than starting from nothing.
Payments sum, across kinds and across providers. One-time payments and subscriptions all contribute to the same total, as do payments made through different payment providers. There is no cap and no ambiguity about which one counts.

Refunds are excluded, not decayed

A refunded payment contributes nothing from the moment it is refunded. It does not fade out politely, because fading would be wrong here: the money went back. This is the one case the decay curve deliberately does not handle, and excluding it outright is what keeps the mechanism honest.

Derived on read, never stored

The tier is computed when it is asked for, from each payment’s amount and its own time anchor. Nothing writes a level anywhere. That single decision carries most of the engineering weight:

No scheduled jobs. There is no nightly task to downgrade anyone, because there is no stored value to downgrade.
Nothing can drift. A stored level is wrong the moment the clock moves past it. A derived one is correct by construction at every read.
Time-dependence is free. Continuous decay is expensive to store and trivial to compute, so the design that computes it is also the simpler one.
The rule lives in one place. Decay and tiering are one function, which makes the whole mechanism a single thing to reason about, test and change.

The first implementation

Graceful Tier Decay first shipped as the Backer Badge in ComeFront, where the summed decaying value maps to a five-level badge. The concrete shape there: each payment counts in full for 30 days, then decays continuously and roughly linearly at about five dollars a week until it reaches zero, and the summed value is tiered into five levels.

The two ends of the range show what the curve does. A single small monthly payment holds its level through the active window and then fades over about a week. A large one-time payment can walk down through the tiers over several months. Those numbers are the calibration of one product, not the mechanism itself. The window, the rate and the tier bands are all parameters.

Impact

For the member

Paying more is worth more, in duration and not only in label
Pausing costs something proportionate instead of everything at once
Coming back builds on what was already given
Past support is remembered for a while rather than erased on a date

For the product

A softer edge on churn: a lapsed member spends the decay period as a visible, partially recognized member rather than as a stranger, which is a far better place to invite them back from.
No renewal cliff to defend: nobody loses their standing overnight, so there is no moment that reliably generates support requests and ill will.
Larger payments become worth making: a member who wants to give more has a reason to, because the extra amount buys real duration.
Less machinery: no cron jobs, no downgrade queue, no stored level to reconcile.

Why the fade is honest

A fading benefit only works if it is understood as recognition of ongoing support rather than as a purchased object. Sell someone a thing and then take it away, and the decay reads as a scam. Recognize someone for supporting a product, and the recognition reasonably tracks how recently and how much they supported it.

The mechanism is honest for the same reason it is useful: it says out loud what every expiry date says quietly, which is that support has a shelf life. Instead of hiding that behind a switch that flips at midnight, it makes the fade visible, gradual and proportionate.

Where it applies

Nothing in Graceful Tier Decay is specific to badges, or to ComeFront. It applies wherever a product turns payments into standing: supporter tiers, membership levels, loyalty status, access levels, priority queues, community roles. The requirements are only that payments have amounts and timestamps, and that the tier can be read rather than stored.

Any product already running an on/off membership can adopt it without changing what it charges or what the tiers mean. It changes one thing: what happens when a member stops paying. Instead of breaking, the membership fades.