Track dunning recovery from failed invoices

Measure failed-payment recovery from invoice failure through retry, card update, recovery, or cancellation for subscription revenue.

Published

difficulty intermediate · time to value 5 minutes
#analytics #revenue #stripe #dunning #churn #saas

Start from this 

Build a dunning recovery funnel: invoice failed → retry scheduled → payment method updated → payment recovered or subscription canceled.

Why this matters

Failed payments are often recoverable churn. A dunning funnel shows whether users update cards, retries recover revenue, or accounts silently cancel.

What you get

  • Recovery rate after failed invoices
  • Time to recovery
  • Cancellations after dunning
  • Revenue at risk and recovered

Walk through it

You

How effective is our dunning flow?

Agent

I’ll stitch billing webhook events into a recovery funnel.

Endpoint: POST /v1/projects/:project_id/analytics/query
Exact shape: /v1/openapi.json?path=%2Fv1%2Fprojects%2F%7Bproject_id%7D%2Fanalytics%2Fquery&method=post
Custom HogQL goes in the OpenAPI-defined `query` field.
Concept fields:
  query: "SELECT event, count(DISTINCT properties.invoice_id) AS invoices, sum(toFloat(properties.amount)) AS amount FROM events WHERE event IN ('invoice_payment_failed','payment_method_updated','invoice_payment_recovered','subscription_canceled') AND timestamp > now() - INTERVAL 60 DAY GROUP BY event ORDER BY invoices DESC"

The output

The agent returns recovery rate, lost revenue, and suggested actions such as improving retry timing or card-update emails.

Setting it up

Emit billing lifecycle events from Stripe or your subscription provider webhook handler.

Variations

  • “Segment recovery by plan.”
  • “Find accounts with repeated payment failures.”
  • “Draft a Slack digest for at-risk revenue.”

Related playbooks

debugging 2 minutes

Diagnose Stripe `card_declined` patterns

Group Stripe payment failures by decline_code. Surface the top causes and the customers affected. Different decline = different fix.

growth 10 minutes

Predict churn 30 days before it happens

Build a behavioral early-warning system that flags at-risk users while there's still time to save them. No ML team required.

growth 3 minutes

Track trial-to-paid conversion by acquisition source

Build the trial-to-paid funnel split by acquisition source. Surface the channel that converts 8x better than the rest.

Adapt this playbook in your own agent.

Ask your agent to map the starter prompt to your saved signal map, live events, and the current HTTP API before answering.

Set up Agentry in this repo by following https://agentry.sh/install.md. I authorize you to: run its device-code login and save the key to ~/.agentry/credentials.json, read this repo, propose an instrumentation plan for my approval, and edit code after I approve it.

+ Full access
5.5 Extra High
  1. 1. Open your repo in Codex, Claude Code, Cursor etc.
  2. 2. Paste the install prompt.
  3. 3. Your agent reads the install doc and shows you an implementation plan for approval.
← all playbooks