composio-community/awesome-gtm-skills/stripe-revenue-report

Stripe Revenue Report

Compute MRR movements from Stripe subscriptions via Composio.

Workflow

1. Scope. Ask for: period (this month, last 30 days, Q2), grouping (plan, segment, geography), format (markdown, Slack, Sheet).
2. Link Stripe:

``bash composio link stripe ``

1. Pull subscriptions + invoices:

``bash composio execute STRIPE_LIST_ALL_SUBSCRIPTIONS -d '{ "limit": 100, "status": "all" }' composio execute STRIPE_LIST_INVOICES -d '{ "created": { "gte": 1714521600 }, "limit": 100 }' ``

1. Classify each MRR delta in the period:

• new — first paid invoice for the customer in the window
• expansion — plan/seat upgrade raising MRR
• contraction — downgrade/seat reduction lowering MRR
• churn — subscription canceled or failed-payment lapse
• reactivation — previously churned, now paying again

1. Compute:

• Starting MRR, New, Expansion, Contraction, Churn, Ending MRR
• Net New MRR = New + Expansion − Contraction − Churn
• GRR = 1 − (Churn + Contraction) / Starting MRR
• NRR = (Starting + Expansion − Contraction − Churn) / Starting

1. Report in the requested format. Always show the component table, not just the headline.

Report template

# Revenue Report — <period>
Starting MRR:   $<x>
+ New:          $<a>    (<n> customers)
+ Expansion:    $<b>    (<n>)
- Contraction:  $<c>    (<n>)
- Churn:        $<d>    (<n>)
Ending MRR:     $<y>
Net New:        $<e>
GRR: <xx>% · NRR: <yy>%
 
Top expansion: <cust> +$<amt>
Top churn: <cust> -$<amt> — reason if known

Guardrails

• Clarify whether "MRR" means normalized monthly (annual / 12) or billed-this-month.
• Failed payments are not churn yet — flag as "at-risk" with dunning status.
• Never post customer-level revenue to public channels without confirming.