All articles

Essay

What an exit scam actually costs to run

Exit scams are not behavioral failures. They are arithmetic. The numbers a vendor watches before walking away are public, and they show up in customer-service latency weeks before the website goes dark.

Most readers think exit scams happen when a vendor gets caught. They happen earlier, and for a duller reason. They happen when the operator runs the arithmetic and decides the next shipment is worth less than the cash already on hand.

That decision is not emotional. It is a present-value calculation, and it is the same calculation the operator was running profitably for the previous eighteen months. The inputs do not change. The only thing that changes is the sign on the answer.

This piece walks through the inputs, names the publicly observable signals each one produces, and points to the one signal a careful buyer can read four to six weeks before the storefront disappears.

What does the operator actually know that the buyer does not?

The operator knows four numbers, each of which is private to them.

Customer-acquisition cost. Most peptide and supplement direct-to-consumer storefronts run paid acquisition through a small set of channels: Reddit promotions, Telegram affiliate programs, a thin coat of search advertising on long-tail queries the major platforms have not yet de-listed. The blended CAC for a recurring buyer in this category sits, in publicly disclosed marketing decks from adjacent supplement categories, somewhere between sixty and one hundred and forty dollars depending on channel mix and content quality.

Lifetime value. The same decks suggest the retention curve falls off sharply after the third refill. A buyer who has not reordered by month four is gone. So the operator is, in effect, paying a one-time fee to get three months of revenue out of a buyer, and the unit economics are good only if the order value clears the CAC by a comfortable margin after fulfillment cost.

Payment-processor reserve. Card-not-present merchants in regulated-adjacent categories typically operate against a held reserve. The reserve is the merchant's own money sitting at the processor, often ten to twenty percent of trailing revenue, released on a rolling schedule. The reserve grows during growth periods and shrinks during contraction. The operator can see the reserve balance on the processor dashboard. The buyer cannot.

Inventory carry. The physical cost of the unshipped stock sitting in the operator's fulfillment closet. For a peptide vendor, this can run from five to fifty thousand dollars at any moment, depending on order velocity and reorder cadence. The operator knows what they paid wholesale. The buyer knows only what they paid retail.

Run those four numbers forward against a constant cost of goods and a slowly decaying brand reputation. The present value of the going concern is the sum of expected future margin minus operating cost. The present value of the alternative is the sum of cash in the bank, plus the value of unshipped inventory the operator can liquidate, minus the cost of a quiet wind-down. There is a date at which the two lines cross. Every operator in this category, honest or otherwise, knows where the lines cross for them. The honest ones stay because their wind-down cost includes a reputation they intend to use again. The dishonest ones do not, and they go on the day the math says go.

What signals does the math produce that a buyer can see?

The behavioral signals show up late. The financial and operational signals show up earlier.

The most reliable of the early ones is customer-service response latency. The reason is operational: the operator's marginal hour of labor is worth more managing the wind-down than answering tickets. Replies that used to come within twelve hours start coming in forty-eight. Then ninety-six. Then they stop. The storefront still takes orders during this entire window, because the order page runs on autopilot and nobody has to type to keep it running. The latency cliff appears in the support inbox first.

A second signal is shipping-time drift. Orders that used to ship within two business days quietly slip to four, then six. The shipping policy on the site does not change, but the actual delivery dates do. Buyers who notice the drift attribute it to seasonal volume or a supply-chain story the seller publishes on the site. By the time the wave of cohorts whose orders never arrive starts complaining publicly, the operator has been gone for two weeks.

A third signal is the disappearance of new product launches. A going concern adds products, runs sales, replies to suggestions. A winding-down concern stops. The blog dies first, then the email cadence, then the product page churn.

None of these are conclusive on their own. Each one has innocent explanations. The pattern is what matters: three signals stacked on the same vendor inside the same six-week window is the shape of an exit.

Why does the buyer need a third party to read the pattern?

Because the buyer cannot see the pattern from inside a single transaction. The operator's customer-service latency is invisible to anyone who has not filed a ticket. The shipping drift is invisible to anyone who has not just ordered. The product-launch flatline is invisible to anyone who is not subscribed to the email list.

What the buyer needs is a witness who is watching every vendor in the category, recording the timing of every signal that any buyer files, and refusing to delete the record when the vendor would prefer the record gone. That witness is what a public registry actually is, when it is built correctly. It is not a review aggregator. It is a clock that runs on every vendor in parallel, and the slope of that clock against the slope of the same vendor a year ago is the early-warning signal that no single buyer can construct alone.

The registry's job is not to predict the exit. The math is the operator's, and the math is private. The registry's job is to make the public-facing slope of each input visible at the category level, so the buyer can compare and decide. A vendor whose response latency triples in four weeks while its peers hold steady is not telegraphing a busy month. It is telegraphing arithmetic.

What follows for a buyer who reads the slope

Three operational changes. None of them require waiting for an exit to be confirmed.

Treat any vendor whose support latency has lengthened by a factor of three in the last six weeks as a vendor on a wind-down clock. Pull existing subscriptions, or at minimum stop adding new ones. The cost of being wrong here is the friction of resubscribing later. The cost of being right is whatever you would have paid in unshipped orders.

Diversify across at least two vendors for any peptide or compounded product that is part of a recurring protocol. The point is not that two vendors are twice as reliable. The point is that the exit-scam math is correlated within a vendor and uncorrelated across vendors, which is the textbook condition for diversification to actually reduce risk.

Pay with instruments that allow a chargeback. Most card-not-present transactions do; most cryptocurrency transactions do not. The decision to accept only payment instruments without chargeback rights is, by itself, a signal worth weighting heavily in the vendor evaluation. The operator knows what the absence of chargeback rights is worth to them. The buyer should ask why.

The exit scam is not a moral failure of the vendor. It is the optimal play once the spreadsheet says so. The fix is not appealing to morality. The fix is making the spreadsheet legible to the buyer, in time.

Frequently asked questions

What is an exit scam in the context of consumer goods?

A pattern in which a seller takes new orders, banks the payments, and then closes operations without shipping. The orders fund the operator's exit rather than the buyer's fulfillment. The pattern is most common in markets where chargebacks are difficult, payment-processor reserves are large, and the seller's brand has limited future value.

Why is customer-service latency the earliest visible signal?

Because the operator stops investing in ticket resolution before they stop investing in the storefront. Replying to a complaint costs labor; the storefront runs on autopilot until DNS expires. The lag between a ticket being filed and a meaningful reply is the cheapest signal a vendor can let slip, and the first one a winding-down operator stops paying.

How long is the typical window between the first detectable signal and full closure?

Across publicly documented exits in adjacent consumer categories, four to six weeks is a common interval between the first cluster of unanswered support tickets and the storefront going dark. The window is long enough to file chargebacks if a buyer notices it, and short enough that most do not.

What does a public registry contribute that a payment processor does not?

A payment processor sees a vendor's own transaction stream. A registry sees the cross-vendor timeline, namely which other operators in the category exited, on what cadence, and how the pre-exit signals looked. The pattern is visible only at the category level, which is where third-party witnesses earn their keep.