The Shutdown Took a Weekend. Regulators Took a Year.
Archi4 min read
Contents
The Shutdown Took a Weekend. Regulators Took a Year.#
The payroll run failed on a Thursday. By Monday the founders had told the staff, parked the domain, and started calling investors about a bridge that would not arrive. The company, a small consumer lending platform described here from the pattern that shows up in public wind-down filings, had eleven employees and roughly 40,000 customers.
The part they underestimated was not the collapse. It was the correspondence.
Eight days after the site went dark, a records preservation request landed. It asked for every version of the marketing page, including the ones replaced in 2023. It asked for the complaint log. It asked for board minutes. It asked for the internal channel where the head of risk had raised a concern about the approval language and then let it drop.
Founders tend to treat compliance as something you produce for a funding round. Regulators treat the same material as evidence of what the company told customers. When the company stops operating, those two readings stop being compatible.
What failed was the bridge, not the model#
Loss rates were inside the plan. The product worked well enough that support tickets were boring. The company died because a term sheet slipped two weeks past the cash-out date, which is the most common cause of death in the sector and the least interesting one to write about.
What made the failure expensive was the sequence that followed. A wind-down is not a private event. It creates a file, and the file is readable by people who write rules for a living.
First contact is a request, not a charge#
Almost no startup gets an enforcement action as its opening regulatory experience. It gets a letter asking it to preserve records, followed by a list. The list is usually short and predictable: , Customer-facing copy, every version, with dates, The complaint log, including items support closed without a ticket, Board and risk committee minutes, Contracts for the model, the data, and the servicing vendor, Internal messages where an employee flagged the problem
The current version of a page tells a regulator very little. The edit history tells them what the company knew and when it changed its wording. Preservation duties begin when a company has reason to think trouble is coming, and "we did not know" is hard to support when a message from nine months earlier says someone did.
Three readers, one file#
A consumer lender in trouble usually hears from three directions. The consumer protection agency cares about the accuracy of claims: approval odds, fee language, the phrase "no credit check." The licensing or prudential regulator cares about customer funds, segregation, and whether a wind-down leaves borrowers mid-transaction. The securities regulator cares about what investors were told and when.
They read the same documents and compare notes. Referrals between agencies are routine. A company that gives one office a clean story and another office a messy one has created the problem it was trying to avoid.
The failure becomes a public document#
This is the part founders miss. A collapse does not end with the company. Agencies publish after-action reviews, supervisors issue letters to the institutions that remain, and staff cite the failure when they draft rules. A single wind-down can surface in a proposed rule two years later as the example of why a disclosure requirement should be mandatory.
For any founder, the useful question is what the file will look like afterward.
What to build before you need it#
A claims register. Every public statement about performance, fees, or approval speed, with the date it went live and the evidence behind it. If marketing cannot point to the evidence, the claim does not ship.
A wind-down plan that names people. Who calls which regulator, who owns the customer email, who holds the vendor keys. Twelve pages is enough.
Segregated customer money with a monthly reconciliation that somebody signs.
An escalation log that lives outside direct messages.
A calendar of rules taking effect in the next eighteen months, not only the ones already in force.
What regulators will probably do next#
Treated as analysis rather than forecast with a date, several patterns look set to continue. Expect more scrutiny of how automated underwriting is explained to applicants who are declined, since a model that cannot be described to a customer is hard to defend in a complaint review. Expect attention to speed claims such as "approved in minutes" when the underlying data does not support them at volume. Expect wind-down and continuity plans to appear as licensing conditions in more jurisdictions, particularly where a platform holds customer balances for even a few hours. Expect individual accountability to keep spreading, because a signature on an attestation is personal and does not transfer to the entity when the entity runs out of cash.
The officers at the company above spent their first month after shutdown learning that a landing page edited four times is four separate documents. Their second month went to personal attestations they had signed without reading closely.
The cheapest fix available is the least popular one: read the attestation before you sign it, and keep the versions.
More articles