FINANCE

Refresh runway scenarios on Snowflake actuals sync

When your nightly Snowflake actuals table updates, recompute base, optimistic, and conservative runway scenarios from real burn and rewrite all three to the Coda model.

CategoryFinance
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule after actuals load
  • ActionQuery trailing cash, revenue, opexSnowflakeSnowflake
  • LogicCompute burn + project 3 scenarios
  • ActionUpsert all scenarios to Coda modelCodaCoda
  • OutputPost scenario digest to SlackSlack

What it does

After your nightly ETL lands fresh actuals in Snowflake, this workflow rebuilds three runway scenarios. It queries trailing cash, revenue, and operating expense, computes net burn, then projects months-of-runway under base, optimistic (revenue up / spend flat), and conservative (spend up / revenue flat) assumptions. All three scenarios are written to the Coda runway model so leadership always sees a current range, not a single guess.

When to use it

Use it when finance reports off a warehouse and the board wants a runway band rather than one number. Good for teams whose actuals are authoritative in Snowflake and who refresh the model on a fixed nightly cadence.

How it works

  1. 1A schedule fires after the nightly actuals load completes.
  2. 2The workflow queries Snowflake for trailing cash, revenue, and opex.
  3. 3Net burn is computed from the actuals window.
  4. 4Three scenarios are projected by flexing revenue and spend assumptions.
  5. 5Base, optimistic, and conservative runway rows are upserted into Coda.
  6. 6A digest of the three scenarios is posted to the finance Slack channel.

Set it up

What you configure once, before turning it on.

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