cus_kraken_logistics
$52000 ARR · renews 2026-09-19 · 120d to renewal
| Factor | Weight | Current | Contribution |
|---|---|---|---|
| payment_history | 0.40 | 0.30 | 0.120 |
| usage_trend | 0.30 | 0.34 | 0.102 |
| champion_status | 0.20 | 0.32 | 0.064 |
| support_sentiment | 0.10 | 0.28 | 0.028 |
| TOTAL | 0.314 (LOW) |
Account health · daily diary from the merged monitor
Diary starts with the next scan
The account-health watcher writes its first entry at the next 06:00 scan. Entries appear here as they're written — verbatim, never summarized.
Timeline · unified account history
No activity yet. As the daily scan, health checks, save plays and renewals accrue, they merge here into one history — newest first.
Evidence · cited signals the worker reasoned over
Evidence from stripe mixpanel-
mixpanel:mp_kraken_usage 2026-05-15
Usage flat within ±6% over 30 days; no power-user drop-off; no support tickets in 21 days.
-
stripe:in_krakenRENEW 2026-05-13
Invoices paid on time for 14 consecutive months; renewal 120 days out.
Raw payload
{ "amount_usd": 52000 }
Diary · longitudinal account memory
First scan — diary builds one paragraph per daily run starting on the next 06:00 UTC tick. After 6 months you have 180 entries; the moat is real and time-based.
Confidence
Medium-HighAll three sources connected — Stripe billing, Slack channel signals, and HubSpot deal context. The worker's classification cites evidence from each source.
Stripe
connected
Slack
connected
HubSpot
connected
Full audit timeline (0 rows)
No audit rows yet.