FINANCE

Weekly Dunning Cadence A/B Tuner

Once a week this workflow analyzes recovery rates of competing retry cadences in BigQuery, picks the winning schedule per customer segment.

CategoryFinance
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionCompute recovery rates per cadence variant in BigQueryGoogle BigQueryBigQuery
  • LogicSelect winning cadence per segment by significance threshold
  • ActionWrite updated cadence config to warehouse tableGoogle BigQueryBigQuery
  • OutputPost cadence-change summary to SlackSlack

What it does

Closes the loop on dunning experimentation. It measures how each retry cadence variant actually recovered failed payments over the trailing weeks, declares a winner per segment, and updates the live cadence configuration so the recovery sequence keeps improving instead of staying static.

When to use it

Run it when you're A/B testing dunning timing (e.g. retry on day 1/3/7 vs day 2/5/10) and want the system to promote winners automatically rather than analysts eyeballing spreadsheets.

How it works

  1. 1A weekly schedule kicks off the analysis.
  2. 2A BigQuery query computes recovery rate and median days-to-recover for each cadence variant, split by plan segment.
  3. 3Logic applies a significance threshold and picks the winning cadence per segment, holding steady when results are inconclusive.
  4. 4The chosen cadence config is written back to the warehouse config table that the dunning workflow reads.
  5. 5A summary of what changed and why posts to Slack for finance visibility.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  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.