cus_cobalt_forge
$58000 ARR · renews 2026-07-07 · 46d to renewal
| Factor | Weight | Current | Contribution |
|---|---|---|---|
| payment_history | 0.40 | 0.30 | 0.120 |
| usage_trend | 0.30 | 0.50 | 0.150 |
| champion_status | 0.20 | 0.68 | 0.136 |
| support_sentiment | 0.10 | 0.55 | 0.055 |
| TOTAL | 0.461 (MED) |
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.
Save play · Tier-2/3 supervised retention recommendation
expected lift: mediumA post-reorg adoption plateau across Amplitude and Segment, a billing contact gone quiet in the CRM, and an open cost-per-seat escalation — the signature of an orphaned account drifting toward churn. A structured handoff session re-seats ownership and re-justifies the spend before renewal.
Anchors · cited evidence source_ids
Evidence · cited signals the worker reasoned over
Evidence from amplitude hubspot zendesk segment stripe-
hubspot:contact_cobalt_maya 2026-05-17
Champion Maya O. changed role to VP Engineering in the CRM; the primary admin seat was not reassigned for 18 days.
-
hubspot:hubspot:contact_cobalt_billing:hs_lastmodifieddate 2026-05-06
Billing contact's last CRM interaction was 16 days ago — no email open, meeting, or note since the reorg announcement.
Raw payload
{ "days_since_activity": 16 }
-
amplitude:amplitude:cus_cobalt_forge:event_count_30d 2026-05-19
Active-feature usage down 27% month-over-month after the Q1 reorg; the three core workflows that drove value last quarter went near-idle.
Raw payload
{ "active_feature_delta_pct": -27 }
-
segment:segment:cus_cobalt_forge:recent_event_types 2026-05-20
Engagement tracking dropout: Segment stopped receiving product events from 9 of 22 instrumented users over the last 14 days.
Raw payload
{ "silent_user_count": 9 }
-
stripe:in_cobaltRENEW 2026-05-16
Upcoming invoice $58,000 due in 46 days; paid on time historically.
Raw payload
{ "amount_usd": 58000 }
-
zendesk:ticket_cobalt_3310 2026-05-18
Escalated support ticket from billing contact: 'We're paying for 22 seats and barely using a third of them — I need to see the cost-per-seat justified before we renew.'
Raw payload
{ "escalated": true, "tag": "cost_per_seat" }
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.