FINANCE

Reforecast Runway on Material Stripe Revenue Shifts

Listens for Stripe subscription and invoice events, and when net new MRR moves beyond a set band it recomputes forward runway and posts the revised projection to Slack.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerStripe subscription / invoice webhookStripeStripe
  • ActionFetch MRR delta and active subscription totalStripeStripe
  • LogicCheck if period delta exceeds material band
  • LogicReforecast forward runway with updated revenue
  • OutputPost revised projection to Slack revenue channelSlack

What it does

Treats your billing system as a live input to runway rather than waiting for month close. When Stripe reports new subscriptions, cancellations, or paid invoices, it recalculates net MRR change for the period and, if the swing is material, reforecasts how runway shifts.

When to use it

Ideal for revenue-led startups where a few large logos or churn events move the runway needle within a month. Use it to catch a big expansion or a painful cancellation before the monthly brief.

How it works

  1. 1A Stripe webhook fires on subscription created, deleted, or invoice paid events.
  2. 2An action pulls the affected MRR delta and the current active subscription total from Stripe.
  3. 3A branch checks whether the cumulative period delta exceeds the material-change band (for example +/- 5% of MRR).
  4. 4If material, recompute forward runway using updated revenue against current burn.
  5. 5Post the revised runway and the triggering event to a Slack revenue channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect StripeCustomers, subscriptions, payments.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.