Cadence admin tables

Comparison of current vs proposed columns for the two admin org tables. Mock data is based on the screenshot snapshot from 18 May.

No sort/filter/search. Once either table has >30 rows it'll be unwieldy. You're at 14/20 now; this gets worse fast. Click-to-sort headers would cost very little to add.
No "at risk" surface. An onboarded customer with no sessions in 21+ days should be loud. A trial ending in <7 days should be loud. Right now you have to scan. Could be a third tab combining stalled-onboarded + trials-ending-soon + scheduled-cancellations.
The split into two tabs is right. Funnel monitoring and active-customer monitoring are different jobs with different signals. Keep that.
Backend changes required are tiny. The existing query already pulls last_session_at — the API mapper just discards it. Expose it. Most other proposed changes are display-only.
Worth adding to the query: subscription_cancel_at_period_end and current_period_end from billing_accounts (for the cancellation pill), and stripe_price_id + per-seat price (for MRR). The columns already exist on the table; they just aren't selected.

Cadence admin tables — review