cus_brixton_labs
$96000 ARR · renews 2026-06-25 · 34d to renewal
| Factor | Weight | Current | Contribution |
|---|---|---|---|
| payment_history | 0.40 | 0.40 | 0.160 |
| usage_trend | 0.30 | 0.86 | 0.258 |
| champion_status | 0.20 | 0.60 | 0.120 |
| support_sentiment | 0.10 | 0.82 | 0.082 |
| TOTAL | 0.620 (HIGH) |
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: highProduct-usage collapse converging with an economic-buyer detractor who cites reliability — a reliability+roadmap exec conversation outranks any discount here.
Anchors · cited evidence source_ids
Evidence · cited signals the worker reasoned over
Evidence from posthog nps stripe-
nps:survey_2026q2_brixton 2026-05-14
Detractor: CTO Devon P. scored 4/10 — 'powerful, but the UI bugs are costing us time'.
-
posthog:ph_brixton_api 2026-05-16
API call volume down 58% month-over-month; the two heaviest integrations went silent on 2026-05-09.
Raw payload
{ "api_delta_pct": -58 }
-
stripe:in_brixtonRENEW 2026-05-18
Upcoming invoice $96,000 due in 34 days; auto-renew on.
Raw payload
{ "amount_usd": 96000 }
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.