Preliminary Findings on Trial Stacking Fatigue
The task of remembering to cancel free trials has grown large enough to deter starting them.
Finding 1: The free trial was designed to reduce friction at the point of acquisition. It has produced friction at the point of cancellation that deters acquisition.
Finding 2: The subject has not started a new free trial in the current quarter. The reason cited is not dissatisfaction with the available services. The reason is the management cost of the cancellation window.
Finding 3: Trial stacking fatigue has become a category in the subject's private threat model for household expenses.
The service feels optional each day while billing treats it as permanent. This asymmetry is the condition that generates fatigue. The subscriber experiences the service as present or absent based on daily use. The billing system experiences the subscriber as a recurring commitment until a specific act of termination occurs. These are two different relationships to the same service running simultaneously.
Trial stacking fatigue survives one more billing cycle for structural reasons. The cost of a single cycle is low enough that the cancellation task feels disproportionately effortful relative to the amount recovered. The household starts planning around the service once it has persisted through two billing cycles. The planning is not an endorsement of the service. It is an accommodation of a fixed line item.
Under the governing rule, trial stacking fatigue becomes procedure once the cancellation task has been deferred twice. At that point, cancellation requires a separate decision rather than following naturally from the trial ending.
A temporary service gains permanent budget status not through a decision to retain it but through the absence of a decision to cancel it. The distinction is significant. Budget reviews address deliberate choices. Trial stacking fatigue produces costs that exist outside the deliberate-choice category.
The preliminary finding is this: the trial model transfers friction rather than eliminating it, and the transferred friction accumulates across multiple services in a way that a single service cannot produce alone. The problem is architectural.