← Outcome Pack

Recover Failed Subscription Payments

Get Superdense

npm i -g @nimrobo/superdense

How to start

Make a folder, start your agent in it, and say: "/outcome-setup set up a Recover Failed Subscription Payments outcome pack for my subscription business."

One-time setup

Connectors

  • Billing provider — pick one: Stripe or Razorpay. It must expose failed payment events, paid/captured recovery events, amounts, timestamps, customer/subscription status, and failure reasons.

Before your first run

  • ☐Install and authenticate the official billing-provider CLI or API access for the account you want to improve.
  • ☐Define the recovery window in goal.md: commonly 7 or 14 days after the first failed payment event.
  • ☐Map provider events before your first run: Stripe `invoice.payment_failed` to `invoice.paid` / `invoice.payment_succeeded`, or Razorpay `payment.failed` to `payment.captured` / `invoice.paid`.
  • ☐Pull the last 30 days of failed payments and record baseline failed amount, recovered amount, failed count, recovered count, and common failure reasons.
  • ☐Confirm where recovery actions happen today: provider retry settings, hosted invoice/payment link, customer portal, or a manual high-value rescue queue.

goal.md

  • North star: % of failed subscription payments that recover within a fixed window, measured from your billing provider's failed-payment event to a paid/captured payment event.
  • Primary metric: recovered failed-payment amount / total failed-payment amount over the window. Track invoice/payment count recovery too, because one large account can hide many unrecovered small failures.
  • Guardrails to consider: do not spam customers, do not over-discount failed payments, and watch support/refund complaints so recovered revenue does not create angry customers.

run.md lever map

  • retry cadence: adjust when failed invoices or subscription payments are retried; diagnostics include recovery rate by retry attempt, median time to recovery, and invoices still open after the recovery window.
  • payment-update path: make the payment method update route obvious and low-friction through the billing provider's hosted invoice, payment link, or customer portal; diagnostics include payment-method updates after failure and recovered amount.
  • dunning message clarity: rewrite the failed-payment notice around continuity of service and one clear action; diagnostics include recovery rate and time-to-paid by message variant.
  • manual rescue queue: review high-value failed payments that remain open after the automated attempts and trigger targeted follow-up; diagnostics include recovered revenue per manual touch and unresolved high-value invoices.

gate.md

Requires Stripe or Razorpay connected, a 30-day baseline of failed and recovered payments recorded, the failed-to-recovered event mapping listed in work.md, one lever changed, and a 7- or 14-day recovery window started. Warning if failure reasons are unavailable or the baseline has fewer than 10 failed payments.