Forced Continuity

Concept

A design where a free trial rolls into a paid subscription on its final day with no warning, so the user finds out after the fact.

Why it exists

A free trial started life as something tilted toward the user. Try it, pay only if you like it — the seller carries the risk. As trials spread, so did the habit of collecting a payment method up front, because asking for a card again after the trial ends loses a large share of people at that exact step.

Collecting the card early is close to a convenience. The trouble arrived with the next decision. Once teams measured that sending a trial-ending email noticeably raised the number of cancellations, the arithmetic pointed at not sending one. So a flow spread across many products: state the end date once in small print near the bottom of the signup screen, then say nothing more. Plenty of users first learn they were charged when the card statement arrives a month later.

Naming the flow was a way of marking it as a choice rather than an oversight. It isn't that there was no way to tell people; someone decided not to. Once the name existed, "isn't this forced continuity?" became a single sentence that could stop the flow in a meeting.

How it works

Take the payment method at signup, put the end date somewhere the user is unlikely to remember it, and run the charge on that date without notice. Each piece looks defensible alone, and the pattern only works once they're assembled.

The flow has four steps.

  1. Collect card details when the trial starts. When "your trial is free" and a card field sit on the same screen, most people move past without thinking hard about the charge that comes later.
  2. Put the end date and the first charge amount somewhere inconspicuous — a line of small grey type at the bottom of the screen, or the last paragraph of the welcome email. It's written down, so nobody can say it wasn't disclosed.
  3. Say nothing as the end approaches. No in-product notice, no email. The silence works best on users who have stopped using the product: they aren't opening the app, so anything placed inside it goes unseen.
  4. Make the charge hard to undo. A clause says the current period isn't refundable; only the next charge can be stopped. By the time most people notice, a month of the subscription is already spent, so the practical choice on offer is whether to lose another one.

The incentive shows up clearly in numbers. Out of 1,000 trial users, sending a notice three days before the end converts roughly 120 to paid, and sending nothing converts 310. A gap of two and a half times is hard for a team to walk back once it has run the test. What's easier to miss is that of those 310, around 190 ask for a refund or dispute the charge with their card issuer inside the first month, and the reviews left along the way sit next to the product name in search results for a long time.

Where it shows up

The phrase turns up most often in trial design meetings for subscription products. Decisions about when to take the card, whether to send a notice before the end, and how many days ahead to send it all get measured against where this label starts to apply. The usual settlement is a notice three days out plus an in-product banner, close enough to the end that the trial is still fresh and early enough that cancelling is not a scramble.

It also comes up in app marketplace review. The major marketplaces require price, billing period, and renewal terms to appear near the purchase button at the same size as everything else, so a screen that pushes them into small type gets rejected. Consumer protection rules have moved the same way, and a growing number of countries now require advance notice before a free trial converts.

Growth experiment reviews raise it as well. At Pagedeck, Ravi proposed removing the notice sent three days before a trial ends as a way to lift paid conversion, and brought a projection in monthly revenue. Mia's objection was arithmetic rather than ethics. Pagedeck is a team product running on auto renewal, where a period ends and the next one starts automatically, so a customer that converts tends to stay for years — and a team that felt tricked at the first charge leaves at the next renewal. Grace kept the email and decided to build a new end-of-trial screen instead.

How it sounds at work

"Dropping the trial-ending email is really a proposal to do forced continuity."

Whatever the intent, the result lands inside that category.

"A billing date that only appears in the terms counts as undisclosed. Put it next to the purchase button at the same size."

Draw the line between having written something and the user being able to see it.

"This isn't forced continuity, it's plain auto renewal. The email goes out three days ahead."

Identical automatic billing gets a different name once notice is part of it.

The screen Pagedeck built carries three things: days left in the trial, the first billing date and amount, and a cancel button that finishes in one click. Noa sized the cancel button the same as the continue button — the opposite move from confirmshaming, where the declining option is shrunk or given wording that makes you feel bad for choosing it.

Four months later paid conversion had slipped a little, as expected, while first-month cancellations and refund requests both fell, leaving more customers at the six-month mark than before. Sofia valued something else: the screen gave her a reason to contact enterprise accounts while their trial was still running.

What people get wrong

The most common misreading is that disclosure in the terms means it isn't forced continuity. Legally defensible and not-this-pattern get treated as the same verdict. But what the label points at isn't whether consent was collected — it's whether the user could realistically know. A sentence skimmed once at signup does not tell anyone about a charge a month later, particularly when the whole point of a trial is that the decision gets deferred. Miss that distinction and a screen that cleared legal review gets called safe, while the refunds and card disputes keep coming from that same screen.

The opposite mistake is treating automatic billing itself as the pattern. Both charge without asking again, which makes them easy to blur. Most subscription products do run on automatic renewal, and forcing users to re-enter payment every month is the worse experience. The dividing line is one thing: notice before the charge. Blur the two and nagging — repeating the same request until someone agrees — gets folded in as well, which hides which screen actually needs fixing.

Easily confused with

TermWhere it blocksHow it differs
Roach motelThe path of someone on the way outMakes a user who wants to cancel work through phone calls and extra steps until they give up. Forced continuity works earlier, by keeping the thought of cancelling from arising at all

Where to go next

  • Dark pattern

    see which of the six branches this type sits in and where the types overlap

  • Confirmshaming

    the neighbor that applies pressure through wording at the moment of choice

  • Auto renewal

    the same automatic billing, and what changes once notice is attached

Last updated 2026-09-16