Weekly cash and runway briefing for your leadership team

Every Monday at 8am, send my leadership team a cash and runway briefing in Slack. Use a scheduled trigger for this, not a poll trigger.

Start by reading my current balances with the Mercury List Accounts operation. Balances live directly on each account as availableBalance and currentBalance, so there is no separate balance lookup to make. Sum the operating accounts to get total cash on hand. Mercury returns monetary amounts as whole dollars in decimal form (12.50 means twelve dollars fifty), so do not divide by one hundred and do not treat these as cents.

Then pull the trailing 90 days of activity with the Mercury List Transactions operation, which reads across all accounts and supports date filtering. Split the results into money in and money out. Average net monthly burn is total money out minus total money in over that window, divided by three. Implied months of runway is total cash on hand divided by average net monthly burn. If the business was net cash positive across the window, say so plainly instead of reporting a negative or infinite runway.

For the week over week change, read the most recent snapshot row already stored in the Google Sheets history tab using the Get Values operation, and compare this week's cash, burn, and runway against it. If the tab is empty because this is the first run, derive last week's cash by taking current cash and reversing the last seven days of transactions, and label the comparison as a first run baseline.

Post the briefing to the leadership Slack channel with the Slack Send a Message operation. Lead with the headline numbers, total cash on hand, average net monthly burn, and months of runway, each with its week over week change. Then call out the two or three vendors or spend categories that moved the most against the prior period and explain why the number shifted, for example a large one off wire, payroll timing, a new vendor ramping up, or an annual renewal landing. Write this as a short narrative briefing a founder can read in thirty seconds. Do not dump the transaction list into the message.

Treat runway below nine months as an explicit warning at the top of the message, since that is the point where founders are advised to start raising. If runway falls below six months, escalate the language further, because options narrow significantly at that point.

Finally, append one snapshot row per week to the Google Sheets history tab with the Append Values operation, capturing the date, total cash on hand, money in, money out, average net monthly burn, and months of runway. One row per week, appended after the numbers are computed, so we build a rolling cash and burn history we can chart later.

A Mercury Read Only token is sufficient for this workflow, since every step only reads data. That also avoids the IP allowlist requirement that Mercury applies to Read and Write tokens.