Amazon employees stared at the Prime cancellation flow they had designed and gave it an internal code name: Iliad. After the Greek epic about a war that grinds on for ten years with no clean end. A system your own team compares to ancient siege warfare is not retention. It is a trap with a revenue number attached to it.

The FTC filed suit against Amazon in mid-2023. Internal documents showed the company knew the design stopped people from leaving. Multiple pages, multiple steps, repeated prompts to reconsider. The complaint alleges Amazon kept the flow running because it held a line on one metric. Monthly numbers looked stable. The subscribers looked loyal.

That is not a retention problem. It is a measurement problem.

"Make cancellation hard and churn goes down." If you run a membership, a coaching program, or any form of recurring billing, someone has said this to you. It sounds like business sense. It is not.

The FTC finalized its Rule Concerning Recurring Subscriptions in late 2024. The compliance deadline lands in mid-May 2025. The rule makes friction-based cancellation illegal for every operator who charges on a recurring basis. Not just Amazon. Every SaaS tool, every coaching membership, every monthly retainer.

The civil penalty: $50,120 per violation. Each customer whose cancellation you mishandle counts as a separate violation. Ten customers trapped is a potential exposure north of half a million dollars. That figure is the published rate under the FTC Act, Section 5(m)(1)(A). It is not a scare number. It is the starting line for enforcement.

Friction-based cancellation does not fail people. It fails the system they are trying to run.

The problem is not that operators want to keep customers. The problem is that friction makes a trapped customer and a loyal customer look the same on a monthly report.

Both produce the same line of revenue. Both show up as active subscribers. But they do not produce the same business. A loyal customer renews because the product earns it. They refer peers. They buy more over time. They cost less to serve each month because they already know how things work.

A trapped customer stays because leaving was too hard. They do not refer. They do not expand. They build resentment that leaks into reviews, support tickets, and charge-backs. And now, under the new rule, each one of them represents a federal liability measured in five figures.

Most people treat this as a personality flaw, some operators being greedy or careless. It is a system flaw. The metric itself hides the gap between trapped and loyal. The FTC just removed the hiding place.

Zakharova said it in her own write-up. After running the full method, she wrote that "authenticity remains the variable no template can supply."

She named the engine. Then kept armoring the wings.

The problem is not that she studied her best work. The problem is that studying only your best work replaces the hard question with an easy one. The easy question: what do my winners share? The hard question: what did posts with the same structure but poor results lack?

Ryan Gartrell framed it well in his March 2026 analysis of survivorship bias in business: "The most valuable question a business leader can ask is not, 'How did they win?' It is, 'Why did others lose?'"

Most people treat this as a creativity problem. It is a measurement problem.

The rule does not ban retention efforts. It bans barriers. There is a provision most small operators have not read. Under 16 CFR 425.6, you get one retention offer. One. You present it clean, with no friction around it. If declined or ignored, cancellation completes right then. Not after one more page. Not after a phone call. Right then.

That single provision is where honest retention lives inside the law. Once that is clear, three moves follow from it.

Strip your cancellation flow to a single page. One button, no maze, no guilt copy, no "are you sure" loops. The FTC defines compliance through what it calls functional equivalence: if signup took three clicks, cancellation cannot take more than three. Count the steps to join. Count the steps to leave. If the second number is higher, you are exposed.

This is the move that costs the most pride and saves the most money.

On that same page, before the cancel button, place one offer. A discount, a pause, a plan change. Whatever fits your model. The customer can take it or skip it. If they skip it, the cancel completes with no added steps. No second offer. No "let me send you to our team." You get one shot, presented clean. That is the full legal space the rule gives you. Use it well or skip it, but do not stack it.

Every cancellation through a clean flow produces a clean signal. When people leave without fighting the process, their stated reasons are real. They are not clouded by anger at the maze itself. Track those reasons. Sort by plan type, by cohort, by weeks since signup. This is the data a trap could never produce. A trap turns every exit into a fight, and a fight tells you nothing about your product.

Running this for 90 days does something the old advice never did:

You see true retention rates, not numbers propped up by friction. You see which save offers actually pull people back, because the data is clean. You see where in the customer arc the drop happens, which tells you what to fix in the product itself. And you see your real monthly number, the one that would survive a federal audit without a six-figure fine behind it.

At the end of 90 days, ask three things:

→ What moved the retention number without friction holding it up?

→ What looked like loyalty but left no trace once the barrier dropped?

→ What reason for leaving showed up more than once?

That is the difference between advice that sounds right and a system that proves itself.

The war that Amazon employees named after ends the way most wars do. Not with a grand win, but with the quiet recognition that the cost of fighting passed the value of holding on a long time ago. A clean exit flow is not a loss. It is the first honest read most operators have ever had on why people stay.

The trap is gone. What it hid is now visible. That is the part worth building on.