Stripe deep-dive lands in Archon

Until last week, Archon’s Stripe integration was a single number: current MRR. Useful, but not enough — the patterns that actually matter (cohort retention, where the churn comes from, which plan is dying) lived in the Stripe dashboard, far from where the advice is generated.

Today the integration is full-depth. Archon reads subscriptions, invoices, payments, customers, and refunds — everything Stripe exposes via its API — and recomputes the metrics you actually need.

What gets computed

1. MRR & ARR — computed from active subscriptions, not paid invoices. Excludes one-time charges. Trial conversions counted from the day the card is captured.
2. Churn rate — rolling 30-day, by count and by revenue. Voluntary vs involuntary (failed payments) flagged separately so you know if the problem is your product or your dunning.
3. Cohort retention — month-by-month curves so you can see whether the people who signed up in February are still around in May.
4. Customer-level health — for each paying customer, last invoice date, plan, MRR contribution, and a flag if their usage pattern suggests they’re about to churn.

How often it syncs

Hourly, in the background. You don’t trigger it. When you open the dashboard, the numbers are at most 60 minutes old. When you ask Archon a Stripe-grounded question, it queries the freshest cached copy.

Permissions

Read-only by default. Archon uses a Stripe restricted key with read permissions on the five resources above and nothing else. It cannot create, modify, or refund anything. You generate the key in your Stripe dashboard and revoke it the same way — one click, takes effect instantly.