The Account Churned on 5 June. The Story Ended on 28 April.

A churned account looks like a single event. The renewal thread goes unanswered. The status flips to Closed Lost. Someone guesses a reason and the room nods.

It was never a single event. It was a trajectory, and every step was time-stamped while it happened.

What the customer said on calls. What they did inside the product. What they typed in the Slack channel where the real decision got made.

Three streams, three tools, and nobody lines them up on the same clock. So the loss looks sudden. Read in order, it was decided five weeks before anyone wrote it down.

---

Each signal alone flatters you

The call team hears enthusiasm and marks the deal healthy. The usage chart shows a dip and shrugs, because dips are noise. The Slack thread is "just chatter."

On its own, every stream has an innocent explanation, and the account stays green right up until it leaves.

Put the three on one timeline and the innocent explanations collapse. Here is the same account, in order.

---

The timeline nobody assembled

• 9 Apr · 10:04  Call
  Kickoff. "We're drowning in untagged customer calls, and nobody synthesizes them." Budget approved.
  The deal enters the pipeline marked healthy, and stays that way for seven weeks.

• 9–10 Apr  Usage
  28 calls imported in the first 48 hours, the last at 01:17. Two saved views built.
  A hands-on evaluator, moving fast. Every leading indicator is green.

• 22 Apr · 15:38  Call
  "I just need something that does one job, really well. I wouldn't get into roadmaps and backlogs."
  The first crack. The breadth on screen reads as bloat to the one person whose budget is open. It goes in the notes as a feature request. It was the first line of the eulogy.

• 28 Apr · 08:12  Usage
  Last login of the week, then nothing. No uploads since the 22nd. The saved views sit untouched.
  The hands went cold. Enthusiasm is now a story the calls still tell and the product has stopped confirming.

• 28 Apr · 23:41  Slack #tooling
  "anyone demo the simpler one? leaning that way, ours is getting complicated."
  Same day as the silence in the product, after hours, the competitor gets a name. Three signals now agree inside twenty-four hours. Risk is critical. The CRM still says healthy.

• 1 May · 16:10  Call
  Reschedules the check-in twice. Replies get shorter. Stops asking about the roadmap.
  Disengaging, politely. The buyer has half-decided.

• 7 May  Slack
  Last message in the channel. After that, quiet.
  The decision is made. Internally, the evaluation is closed.

• 5 Jun · 09:03  Silence
  No reply on the renewal thread. The account flips to Closed Lost. Reason field: timing.
  The only inaccurate line in the whole record. Timing was the alibi. The cause was written on 22 April and confirmed on the 28th.

---

The verdict had a date

No single stream caught it. The calls sounded fine through 1 May. The usage drop on 28 April was noise on its own. The Slack line was chatter. Read together, in order, the three cross on 28 April, and the read is unambiguous with five weeks left to act on it.

The data was always there, scattered across three tools and three timestamps. The story only exists once something puts the milestones in order and says what each one meant.

---

The same timeline, stopped at today

A post-mortem assembles this after the account is gone. You read it standing over the loss.

/pre-mortem assembles the identical timeline for an account that is still live, and stops it at today. Same three signals, same crossing point, same escalating read, ending on the one move still on the table. Run on this account on 28 April, it reads:

Scope mismatch on the last call. Usage cooling. A named competitor in the channel. Strip the demo to the one job and call them this week.

Most of your quiet accounts are mid-timeline right now. The milestones are landing in three different tools, time-stamped, and no one is reading them in order.

We built Fragment to assemble the timeline while you can still change its ending.

See the timeline your quiet accounts are writing right now.