stripe-revenue

Extract and compute MRR, cohort revenue, LTV, and churn diagnostics from Stripe data.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/DojoCodingLabs/GTM-Engineering-Command-Center --skill stripe-revenue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stripe-revenue
Source: https://github.com/DojoCodingLabs/GTM-Engineering-Command-Center/tree/main/skills/stripe-revenue
Command: npx skills add https://github.com/DojoCodingLabs/GTM-Engineering-Command-Center --skill stripe-revenue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual revenue reporting and fragmented billing data hide true subscription health, causing incorrect MRR, LTV, and churn decisions for SaaS teams. This Skill centralizes Stripe subscription and invoice data, normalizes billing intervals, applies discounts, and produces accurate recurring revenue metrics and diagnostics that finance and growth teams can act on.

Core Features & Use Cases

  • MRR Calculation: Normalize subscription prices across billing intervals, apply coupon/discount logic, and aggregate active (including trialing and past_due) subscription MRR.
  • Cohort Revenue Analysis: Build monthly cohort revenue tables, normalized retention curves, and visualizations to reveal retention quality and expansion/contraction patterns.
  • LTV & CAC Insights: Compute simple, margin-adjusted, cohort-based, and probabilistic LTV estimates plus CAC payback and channel-segmented LTV:CAC ratios.
  • Churn Diagnostics & Webhook Tracking: Classify voluntary vs. involuntary churn, implement dunning/pre-dunning workflows, and track MRR movements via subscription webhooks.
  • Use Case: Run a monthly revenue audit to detect hidden churn, quantify expansion revenue, and prioritize fixes to improve payback period and LTV.

Quick Start

Connect your Stripe account and run a revenue audit to compute normalized MRR, generate cohort revenue tables, calculate LTV and payback period, and surface top churn drivers.

Frequently Asked Questions about stripe-revenue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I calculate MRR from Stripe subscriptions with different billing intervals?

To calculate MRR from Stripe subscriptions, normalize prices across monthly and annual billing intervals, apply active coupon and discount logic, and aggregate trialing, active, and past_due subscription values into a single monthly recurring revenue snapshot.

How do I build a cohort revenue analysis from Stripe invoice data?

Building a cohort revenue analysis from Stripe invoices involves grouping customers by their initial billing month, tracking subsequent monthly revenue, and generating retention curves to visualize expansion, contraction, and churn patterns over time.

What's the best way to track voluntary versus involuntary churn in Stripe?

Tracking Stripe churn involves classifying subscription cancellations as voluntary or involuntary, implementing dunning workflows for failed payments, and using webhook events to monitor MRR movements and identify top churn drivers.

Do I need Stripe webhook events to compute accurate LTV and MRR movements?

Yes, tracking MRR movements and computing accurate LTV requires Stripe webhook events to capture real-time subscription updates, prorations, and cancellations that standard invoice polling might miss between billing cycles.

How do I calculate cohort-based LTV and CAC payback for SaaS subscriptions?

Calculating cohort-based LTV and CAC payback requires grouping Stripe customers by acquisition channel, computing margin-adjusted lifetime revenue per cohort, and dividing the customer acquisition cost by the monthly cohort revenue to determine the payback period.

Does this approach handle Stripe prorations and discounts when normalizing recurring revenue?

Yes, accurate recurring revenue normalization requires applying proration and discount handling logic to Stripe invoices, ensuring mid-cycle upgrades, downgrades, and coupon applications do not skew monthly MRR snapshots.