FINANCE

Cohort margin erosion tracker synced to Coda board

Pulls quarterly cohort gross margin from BigQuery and upserts each cohort's trend into a Coda table so finance can review and annotate erosion in a living board.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerQuarterly schedule after quarter close
  • ActionQuery BigQuery cohort margin (current + prior quarter)Google BigQueryBigQuery
  • LogicCompute delta and assign erosion status
  • ActionUpsert each cohort row into Coda tableCodaCoda
  • OutputRefresh Coda summary viewCodaCoda

What it does

Reads cohort-level gross margin history from BigQuery and writes a tidy row per cohort into a Coda table, including current margin, prior-quarter margin, and a computed erosion flag. The Coda board becomes the single shared surface where finance reviews, comments, and tracks remediation owners over time.

When to use it

Use it when a Slack ping isn't enough and you need a durable, editable record of which cohorts are decaying, who owns the fix, and whether last quarter's intervention worked. Good for teams that run margin reviews inside Coda docs.

How it works

  1. 1A scheduled trigger runs after each quarter close.
  2. 2A BigQuery query returns gross margin per cohort for the current and prior quarter.
  3. 3A logic step computes the erosion delta and assigns a status (stable, watch, eroding).
  4. 4Each cohort row is upserted into the Coda table, keyed by cohort id, preserving any human-added owner and notes columns.
  5. 5A final output step refreshes a Coda summary view so the board reflects the latest run.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect CodaDocs, packs, automations.
  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.