FINANCE

Build a weekly refund-by-cohort scorecard and post it to the team

Every Monday, aggregates the prior week's Stripe refunds by merchant cohort in Snowflake, ranks cohorts by week-over-week refund-rate change.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly Monday schedule
  • ActionPull trailing two weeks of refunds from StripeStripeStripe
  • ActionAggregate per-cohort refund rate by week in SnowflakeSnowflakeSnowflake
  • LogicRank cohorts by week-over-week delta, tag movers
  • OutputPost cohort scorecard to finance SlackSlack

What it does

Produces a recurring health scorecard of refund behavior across every merchant cohort. Rather than alerting on individual outliers, it gives finance a portfolio-level view of which cohorts are trending up or down on refunds and by how much, week over week.

When to use it

Use this for the standing weekly finance review. It answers "where is refund pressure building across the book" in one glance, so leadership can prioritize which cohorts to dig into before any single merchant trips an alert.

How it works

  1. 1A weekly schedule fires Monday morning.
  2. 2Pull the trailing two weeks of refunds and charges from Stripe.
  3. 3Aggregate refund rate per cohort for each week in Snowflake.
  4. 4Rank cohorts by week-over-week refund-rate delta and tag the top movers.
  5. 5Render a scorecard table with current rate, prior rate, and delta per cohort.
  6. 6Post the scorecard to the finance Slack channel and pin the biggest movers.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect StripeCustomers, subscriptions, payments.
  2. 2
    Connect SnowflakeWarehouses, queries, shares.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.