Demo company data — fictional business, real briefing format.
Laurent, cash sits at $487,224, down $28,930 on the week. Almost entirely receivables timing — two invoices slipped past due. Your 13-week low is $61,480, and on current timing you cross your $150,000 buffer the week of Jul 20. Two of the three actions below move that date.
- −$34.4kAcme Industrial (INV-1041, $22,900) and Corvid Media (INV-1038, $11,500) both slipped past due. Acme has paid day-45 on its last three invoices — forecast re-dated to match, not to the due date.
- +$8.2kBluepeak Services paid early. Their observed behavior is day-12 on Net-30 — your fastest payer.
- −$2.7kNew recurring charge detected: Datadog moved from monthly to annual billing. Reconciled against the AP register so it is not counted twice.
- Send reminders to 11 late clients — $17.3k overdue, of which $14.1k sits with three clients who historically pay within a week of a nudge.≈ +2 wks
- Defer 8 non-critical bills — $40.2k flagged deferrable without vendor risk, based on payment history and terms.≈ +6 wks
- Review a possible duplicate charge — $2.4k to the same vendor twice in 9 days, different references. Caught by reconciliation, not by chat.$2.4k
What you just read, annotated
The letter leads with the one date that matters. Not “runway: 9 months” — a buffer-breach week, with its cause. Everything else in the briefing exists to move that date or explain it. That's the difference between reporting and deciding. For most businesses this size, the breach week is the week the line of credit quietly gets drawn — the briefing's job is to make that draw a decision made five weeks early, not a surprise made at the bank.
Every change is attributed. “Down $28,930” is a fact; which invoices, and what those clients' observed payment behavior says is an explanation. XPlor re-dates receivables from how each customer actually pays — the day-45 client is forecast at day 45, whatever the invoice says.
The actions carry modeled deltas. “≈ +6 wks” isn't decoration — it's the server recomputing the forecast with those eight bills deferred. Click it in the product and you can commit the scenario into your real assumptions. An alert tells you there's a problem; a lever changes the outcome.
The duplicate catch came from reconciliation. A recurring-payment engine that cross-checks the AP register is what notices the same obligation twice. Asking a chatbot “any duplicate charges?” produces an answer; a reconciliation layer produces this line, unprompted, every week.
And one thing this page deliberately is: an output, not a mockup. This is the format design partners receive — with their numbers where the demo company's are. The words are the product. The forecast underneath them is graded every Monday.