FINANCE
Severe cohort-margin erosion PagerDuty escalation
Runs a BigQuery margin check and, only when a high-value cohort erodes past a severe threshold, triggers a PagerDuty incident and logs the event to a Postgres audit table.
How it runs
The automated pipeline, trigger to output.
- TriggerQuarterly schedule after quarter close
- ActionQuery BigQuery cohort margin and revenueBigQuery
- LogicGate on severe erosion AND material revenue
- ActionTrigger PagerDuty incident per qualifying cohortPagerDuty
- OutputWrite escalation to Postgres audit tablePostgres
What it does
This is the escalation tier for cohort-margin erosion. It checks BigQuery for cohorts crossing a severe decline threshold, but escalates only when the eroding cohort also carries material revenue, avoiding noise. When both conditions hold, it opens a PagerDuty incident and records the event to a Postgres audit table.
When to use it
Use it when certain cohorts are large enough that a quiet margin collapse warrants paging the finance on-call, not a Slack message that waits until Monday. The revenue gate ensures only consequential erosions trigger a page.
How it works
- 1A scheduled trigger runs after quarter close.
- 2A BigQuery query returns per-cohort gross margin and the cohort's trailing revenue.
- 3A logic step applies a two-condition gate: severe erosion AND revenue above the materiality floor.
- 4For each cohort passing the gate, a PagerDuty incident is triggered with the cohort detail and severity.
- 5An output step writes the escalation to a Postgres audit table for compliance and post-incident review.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Finance workflows
Detect Annual-to-Monthly Downgrade Refunds Owed
Catches subscriptions switched from an annual term to monthly partway through the prepaid year, computes the unused prepaid balance owed back.
Detect Mid-Cycle Plan Change Mischarges and Queue Credit Memos
Listens for Stripe subscription plan changes, recomputes the correct prorated amount.
Expense Submission Webhook Instant Triage and Routing
Receives each expense submission via webhook the instant it's filed, classifies it as in-policy, needs-review, or hard-violation, and routes it to auto-approval.
Accrual Chase Board in Monday with Per-Owner Tasks
On a schedule it reads open uncoded expenses from Snowflake and creates or updates a Monday item per department owner.
Real-Time Uncoded Expense Nudge on New Spend Event
When a new expense lands without a GL code, a webhook fires and the workflow immediately Slack-nudges the spending owner to code it on the spot.
Monthly Vendor Spend Anomaly Brief for Finance Leads
Once a month, an agent analyzes the full expense ledger for vendor and category spend anomalies, drafts a narrative brief with the top outliers and likely causes.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.