FINANCE

Runway-breach alert when projected months drop below threshold

Runs daily against BigQuery, and when projected runway falls under a set number of months it emails finance leadership a focused alert with the driver behind the drop.

CategoryFinance
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule fires
  • ActionQuery current cash and burn trend from BigQueryGoogle BigQueryBigQuery
  • LogicCompute runway and check against threshold floor
  • ActionIsolate the largest spend driver behind the dropGoogle BigQueryBigQuery
  • OutputEmail leadership a runway-breach alert via OutlookOutlook

What it does

It checks projected runway against a configured floor (for example, nine months) every day. Most days nothing happens. On the day runway crosses below the threshold, it identifies the largest contributor to the change and emails leadership a concise alert via Outlook so action is taken before the next board cycle.

When to use it

When you want an early-warning tripwire rather than a routine report. Best for teams whose burn can shift fast (hiring waves, infra spikes) and who need to know the moment runway dips into the danger zone.

How it works

  1. 1A daily schedule triggers the check.
  2. 2It queries BigQuery for current cash and the latest burn trend.
  3. 3It computes projected runway in months.
  4. 4A branch checks whether runway is below the configured threshold; if not, the run ends silently.
  5. 5If breached, it isolates the biggest week-over-week spend driver from the BigQuery data.
  6. 6It sends an Outlook email to finance leadership with the new runway number, the threshold crossed, and the primary driver.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect OutlookMail, calendar, contacts.
  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.