cus_meridian_pay
$28000 ARR · renews 2026-07-19 · 58d to renewal
| Factor | Weight | Current | Contribution |
|---|---|---|---|
| payment_history | 0.40 | 0.18 | 0.072 |
| usage_trend | 0.30 | 0.22 | 0.066 |
| champion_status | 0.20 | 0.20 | 0.040 |
| support_sentiment | 0.10 | 0.15 | 0.015 |
| TOTAL | 0.193 (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.
Save play · Tier-2/3 supervised retention recommendation
expected lift: mediumSustained 3.2x usage growth plus an inbound SOC 2 request — a warm, customer-initiated security add-on expansion.
Anchors · cited evidence source_ids
Evidence · cited signals the worker reasoned over
Evidence from posthog inbound email stripe-
conversation:email_meridian_soc2 2026-05-15
On the 2026-05-15 QBR the team asked about the SOC 2 add-on for an upcoming enterprise deal of theirs.
-
posthog:ph_meridian_api 2026-05-18
API calls running 3.2x baseline for six straight weeks; premium endpoints are driving the growth.
Raw payload
{ "api_multiple": 3.2 }
-
stripe:in_meridianRENEW 2026-05-17
On-time payment history; renewal in 58 days.
Raw payload
{ "amount_usd": 28000 }
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.