One question splits the whole delay
Operations engineers have a standard question for any delay: is it imposed by physics, or by process? A metallurgical cure time is physics. A form that waits for Thursday's sign-off meeting is process. The distinction matters because only the second kind is negotiable, and organisations that never separate the two end up treating the whole delay as a law of nature.
Run a trading firm's retention delay through that question and it separates cleanly.
When a trader takes a loss that matters, the response is fast. The body's fast stress arm releases catecholamines in seconds, and they clear within a couple of minutes. The behaviour rides that curve: traders who revenge trade typically re-enter within a minute of the loss, at larger size. We operationalise the space between trigger and next trade as a window of roughly four minutes. The physiology is measured science. The re-entry pattern is what firms see in their own fills. The four-minute figure is our working construct built on both, and we label it as such.
That is the whole physics half. Everything else in the delay belongs to the other column.
The clocks the firm chose
Walk through what a standard operation runs between a trigger and a response, and note when each one fires.
The one control that moves at event speed is the max-loss lockout, and it deserves its credit: it fires the instant losses cross the line. But it is positioned at the end of the sequence, enforcement at the crash boundary rather than intervention before it. It is real time at the wrong moment.
After the lockout, the clocks get long. The retention or support desk works business hours in one timezone. The trader's journal gets reviewed that evening, if it gets reviewed. The analytics dashboard is read the next morning, or on Monday. The cohort report lands monthly. The lapse flag, the one that says a funded trader has gone quiet, fires weeks after the behaviour that caused it. Every tool in that list works, and we have written before about the window they all miss. This post is about what stands between a firm and that window: each tool works on its own clock, and none of those clocks was chosen against the event it is meant to catch. At the macro scale the same gap shows up as the silence between the challenge sale and the blow-up. They are inherited cadences: office hours, reporting cycles, the rhythm of the working week, applied to a behaviour that completes before the kettle boils.
The latency ledger
Put the clocks in one table and label each one.
| Clock | Typically fires | Physics or process? |
|---|---|---|
| Stress response | Seconds after the trigger | Physics |
| Next trade after a loss | Often under a minute | Observed behaviour, riding the physics |
| The intervention window | ~4 minutes | Our operational construct, built on the two rows above |
| Max-loss lockout | Instant, at the loss boundary | Process, positioned last |
| Retention / support desk | Business hours | Process |
| Journal review | That evening, up to ~19 hours | Process |
| Dashboard review | Next morning or Monday | Process |
| Cohort report | Up to 30 days | Process |
| Lapse flag | Weeks after the behaviour | Process |
The arithmetic makes the table concrete. A trigger fires at 2:14am: three losses, a re-entry at double size, the shape every risk desk recognises. A desk that opens at 9:00 in the firm's home timezone can first act six hours and forty-six minutes later. Call it seven hours. The behaviour it needed to reach completed before 2:20am.
The assumption is stated so you can attack it: one desk, one timezone, 9 to 6. A firm running follow-the-sun coverage shrinks the number. It does not change the column the desk sits in, because the smallest process clock in the stack is still measured in hours, against an event measured in minutes.
Behavioural spirals of exactly this shape sit behind the churn that removes roughly 75% of retail traders inside 90 days. The delay is not a detail of the problem. On the intervention side, the delay is most of the problem.
The industry already thinks this way, once
Trading has one of the most sophisticated latency cultures in any industry. Firms publish guides for shaving execution latency to a millisecond. Infrastructure vendors advertise tick-to-trade in microseconds. Evaluation rules police holding times measured in seconds. On the execution path, the sector treats every millisecond as negotiable and hunts it without mercy.
Then the same firms run the intervention path on office hours and monthly reports, and describe the result as just how retention works.
The engineering instinct is not missing. It has been pointed at one side of the business and never at the other. Nobody decided that a tilting trader should wait seven hours for a human process; the clocks were never audited, because the total was never split into the half that is fixed and the half that is chosen.
An afternoon's audit
The exercise costs an afternoon. List every clock in your retention stack: every control, review, report and flag that could touch a struggling trader. Write down when each one actually fires relative to a trigger, not when the vendor deck says it does. Label each row physics or process.
Most firms that run this exercise find a fixed trader-side clock they cannot move, one fast control positioned after the damage, and every remaining row sitting in the process column with a cadence nobody can defend beyond precedent. What a firm does with that finding varies. Some re-sequence what they already own: alerts routed to whoever is awake, reviews moved closer to the session. The last gap, the minutes between trigger and next trade, is the one no review cadence reaches, and it is the specific gap Discentra exists to close: detection on the trade feed, and a coaching call that arrives inside the window. Coaching, not financial advice.
But the audit stands on its own. Most of the clocks in the ledger were never chosen by anyone, and an afternoon of labelling them is how a firm finds out which ones it can change.
