How Stripe MRR Movement Intelligence Automates Revenue Analysis

Your CFO asks for a cash flow variance report by end of day. The data lives in Stripe, Notion, Slack — transactions in one, forecasts in another, vendor commitments in a third. Someone pulls each export, reconciles the numbers in a spreadsheet, flags the anomalies, and writes a narrative. This process takes 2–4 hours weekly. By the time the report lands, the numbers are 48 hours stale.

The problem is not the analysis itself — it is the lag between data and decision. Cash flow visibility is always retrospective. Vendor risk concentrations are discovered during audits, not in real time. Revenue trends are reported monthly when they should be monitored weekly. Stripe MRR Movement Intelligence automates the revenue analysis and financial analysis workflow, converting raw Stripe, Notion, Slack data into structured intelligence on a recurring schedule.

Four Agents. Monthly MRR Waterfall. Revenue Narrative.

The Stripe MRR Movement Intelligence pipeline runs 4 agents in sequence. The Fetcher pulls data from Stripe and Notion and Slack, and The Formatter delivers the output. Here is what happens at each stage and why it matters.

• The Fetcher (Code-only): Retrieves subscription-level event data from Stripe API for the current and prior months — subscription created, updated, canceled, and reactivated events, invoice amounts, customer metadata, plan details, and discount codes.
• The Assembler (Code-only): Constructs the MRR waterfall across 5 movement buckets: New (first-time subscriptions), Expansion (plan upgrades and seat additions), Contraction (downgrades and seat removals), Churn (canceled subscriptions), and Reactivation (returning customers).
• The Analyst (Tier 2 Classification): Analyzes MRR movements for revenue narrative: what drove growth or contraction, which customer segments contribute most to each bucket, concentration risk from top accounts, churn pattern identification (voluntary vs.
• The Formatter (Tier 3 Creative): Generates a Notion monthly MRR intelligence report with waterfall visualization data, bucket breakdowns, concentration analysis, churn patterns, and trajectory projection, plus a Slack digest with MRR movement summary and top 3 revenue actions..

When the pipeline completes, you get structured output that is ready to act on. The blueprint bundle includes everything needed to deploy, configure, and customize the workflow:

• ITP-tested n8n workflow (28 nodes + 3-node scheduler)
• 5-bucket MRR waterfall (New, Expansion, Contraction, Churn, Reactivation)
• Concentration risk analysis from top accounts contributing to each bucket
• Churn pattern identification (voluntary vs. involuntary, early vs. mature cohorts)
• Expansion driver analysis showing which plan upgrades and seat additions contribute most
• 3-month MRR trajectory projection based on current movement trends
• Customer segment breakdown per waterfall bucket
• Notion monthly MRR intelligence report with waterfall data and revenue narrative
• Slack digest with MRR movement summary and top 3 revenue actions
• Configurable: plan grouping, concentration thresholds, cohort definitions, lookback period
• Full technical documentation and system prompts

All scoring criteria, output formats, and routing rules are configurable in the system prompts — no workflow JSON edits required. This means Stripe MRR Movement Intelligence adapts to your specific process, terminology, and integration requirements without forking the entire workflow.

Understanding how the pipeline works helps you customize it for your environment and troubleshoot issues when they arise. Here is a step-by-step walkthrough of the Stripe MRR Movement Intelligence execution flow.

Step 1: The Fetcher

Tier: Code-only

The pipeline starts here. Retrieves subscription-level event data from Stripe API for the current and prior months — subscription created, updated, canceled, and reactivated events, invoice amounts, customer metadata, plan details, and discount codes. Pulls historical MRR snapshots for waterfall construction.

This stage ensures all downstream agents receive clean, validated input. If this step returns incomplete data, every downstream agent works with a degraded picture.

Step 2: The Assembler

Tier: Code-only

Constructs the MRR waterfall across 5 movement buckets: New (first-time subscriptions), Expansion (plan upgrades and seat additions), Contraction (downgrades and seat removals), Churn (canceled subscriptions), and Reactivation (returning customers). Computes concentration risk, churn patterns by cohort, and trajectory projection.

Why this step matters: The result is a prioritized action queue, not just a data dump.

Step 3: The Analyst

Tier: Tier 2 Classification

Analyzes MRR movements for revenue narrative: what drove growth or contraction, which customer segments contribute most to each bucket, concentration risk from top accounts, churn pattern identification (voluntary vs. involuntary, early vs. mature), and 3-month trajectory projection based on current trends.

Every field in the output is structured for the next agent to consume without parsing.

Step 4: The Formatter

Tier: Tier 3 Creative

This is the final deliverable — what lands in your inbox or dashboard. Generates a Notion monthly MRR intelligence report with waterfall visualization data, bucket breakdowns, concentration analysis, churn patterns, and trajectory projection, plus a Slack digest with MRR movement summary and top 3 revenue actions.

The entire pipeline executes without manual intervention. From trigger to output, every decision point follows a documented path. Every execution produces a traceable audit trail.

All nodes have been validated during Independent Test Protocol (ITP) testing on n8n v2.7.5. The error handling matrix in the bundle documents the recovery path for each failure mode.

Models wrap JSON in markdown code fences even when told not to. The prompt says "respond with raw JSON only" and the model responds with ```json\n{...}\n```. Every parser in every blueprint strips markdown fences before calling JSON.parse. It is not a bug — it is a known model behavior you must design around.

— ForgeWorkflows Engineering

Monthly MRR waterfall analysis with 5 movement buckets, concentration risk, churn pattern identification, and trajectory projection delivered via Notion and Slack.

The primary operating cost for Stripe MRR Movement Intelligence is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Run: $0.05–$0.10 per run. This figure includes all API calls across all agents in the pipeline — not just the primary reasoning step, but every classification, scoring, and output generation call.

To put this in context, consider the manual alternative. A skilled team member performing the same work manually costs $75–100/hour for a finance analyst at a fully loaded rate (salary, benefits, tools, overhead). If the manual version of this workflow takes 2–4 hours weekly, the per-execution cost in human labor is significant. The blueprint executes the same pipeline for a fraction of that cost, with consistent quality and zero fatigue degradation.

Infrastructure costs are separate from per-execution LLM costs. You will need an n8n instance (self-hosted or cloud) and active accounts for the integrated services. The estimated monthly infrastructure cost is Monthly cost ~$0.05-0.10/run, depending on your usage volume and plan tiers.

Quality assurance: Blueprint Quality Standard (BQS) audit result is 12/12 PASS. ITP result is 8/8 records, 14/14 milestones. These are not marketing claims — they are test results from structured inspection protocols that you can review in the product documentation.

All cost and performance figures are ITP-measured — tested against real data fixtures on n8n v2.7.5 in March 2026. See the product page for full test methodology.

6 files. Main workflow + scheduler + prompts + docs.

When you purchase Stripe MRR Movement Intelligence, you receive a complete deployment bundle. This is not a SaaS subscription or a hosted service — it is a set of files that you own and run on your own infrastructure. Here is what is included:

• CHANGELOG.md — Version history
• README.md — Setup and configuration guide
• docs/TDD.md — Technical Design Document
• stripe_mrr_movement_intelligence_scheduler_v1_0_0.json — Scheduler workflow
• stripe_mrr_movement_intelligence_v1_0_0.json — n8n workflow (main pipeline)
• system_prompts/analyst_system_prompt.md — Analyst system prompt
• system_prompts/formatter_system_prompt.md — Formatter system prompt

Start with the README.md. It walks through the deployment process step by step, from importing the workflow JSON into n8n to configuring credentials and running your first test execution. The dependency matrix lists every required service, API key, and estimated cost so you know exactly what you need before you start.

Every file in the bundle is designed to be read, understood, and modified. There is no obfuscated code, no compiled binaries, and no phone-home telemetry. You get the source, you own the source, and you control the execution environment.

Stripe MRR Movement Intelligence is built for Finance, Leadership teams that need to automate a specific workflow without building from scratch. If your team matches the following profile, this blueprint is designed for you:

• You operate in a finance or leadership function and handle the workflow this blueprint automates on a recurring basis
• You have (or are willing to set up) an n8n instance — self-hosted or cloud
• You have active accounts for the required integrations: Stripe account with subscription billing, Anthropic API key, Notion workspace, Slack workspace (Bot Token with chat:write)
• You have API credentials available: Anthropic API, Stripe (API key, secret key), Slack (Bot Token, httpHeaderAuth Bearer), Notion (httpHeaderAuth Bearer)
• You are comfortable importing a workflow JSON and configuring API keys (the README guides you, but basic technical comfort is expected)

This is NOT for you if:

• Does not modify subscriptions or invoices in Stripe — read-only analysis of subscription events
• Does not replace financial reporting tools — it adds movement intelligence and concentration analysis
• Does not forecast exact MRR numbers — trajectory projection is trend-based, not predictive modeling
• Does not handle non-subscription revenue — one-time charges and usage-based billing are excluded
• Does not send dunning emails — use Stripe Dunning Intelligence (#29) for failed payment recovery

Review the dependency matrix and prerequisites before purchasing. If you are unsure whether your environment meets the requirements, contact support@forgeworkflows.com before buying.

Every pipeline has boundaries. These are intentional design decisions, not oversights — understanding them helps you deploy with the right expectations and plan for edge cases in your environment.

Does not modify subscriptions or invoices in Stripe — read-only analysis of subscription events

This is intentional. We default to human-in-the-loop for actions that carry reputational or financial risk. Once your team has validated output accuracy over 20+ cycles, you can adjust the pipeline to auto-execute — the workflow JSON supports it, but the default is conservative.

Does not replace financial reporting tools — it adds movement intelligence and concentration analysis

We scoped this boundary after ITP testing revealed inconsistent results when the pipeline attempted this. The agents handle what they handle well — extending beyond this scope requires custom prompt engineering specific to your data shape.

Does not forecast exact MRR numbers — trajectory projection is trend-based, not predictive modeling

This keeps the pipeline focused on a single workflow. Adding this capability would introduce branching logic that varies by organization, and the tradeoff between complexity and reliability was not worth it for a reusable blueprint. Fork the workflow JSON if your use case demands it.

Deployment follows a structured sequence. The Stripe MRR Movement Intelligence bundle is designed for the following tools: n8n, Anthropic API, Stripe, Notion, Slack. Here is the recommended deployment path:

1. Step 1: Import workflows and configure credentials. Import both workflow JSON files into n8n (main + scheduler). Configure Stripe API key (secret key), Notion API token (httpHeaderAuth with Bearer prefix), Slack Bot Token (httpHeaderAuth with Bearer prefix, chat:write scope), and Anthropic API key following the README.
2. Step 2: Configure plan grouping and thresholds. Set PLAN_GROUPS (mapping of Stripe price IDs to plan names), CONCENTRATION_THRESHOLD (default 0.2), CHURN_COHORT_MONTHS (default 3 for early churn), NOTION_DATABASE_ID, and SLACK_CHANNEL in the scheduler Build Payload node.
3. Step 3: Activate scheduler and verify. Update the webhook URL in the scheduler to match your main workflow webhook path. Activate both workflows. Send a test POST with _is_itp: true and sample subscription data. Verify the MRR report appears in Notion and the digest appears in Slack.

Before running the pipeline on live data, execute a manual test run with sample input. This validates that all credentials are configured correctly, all API endpoints are reachable, and the output format matches your expectations. The README includes test data examples for this purpose.

Once the test run passes, you can configure the trigger for production use (scheduled, webhook, or event-driven — depending on the blueprint design). Monitor the first few production runs to confirm the pipeline handles real-world data as expected, then let it run.

For technical background on how ForgeWorkflows blueprints are built and tested, see the Blueprint Quality Standard (BQS) methodology and the Inspection and Test Plan (ITP) framework. These documents describe the quality gates every blueprint passes before listing.

Ready to deploy? View the Stripe MRR Movement Intelligence product page for full specifications, pricing, and purchase.